<!DOCTYPE html>
<html class="client-nojs vector-feature-night-mode-disabled vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-sticky-header-enabled" lang="en" dir="ltr"><head>
<meta charset="UTF-8">
<title>Byte</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="canonical" href="https://en.wikipedia.org/wiki/Byte"> <link href="./mw/ext.cite.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.icons.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.search.codex.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/user.styles.css" rel="stylesheet" type="text/css">
<meta name="ResourceLoaderDynamicStyles" content="">
<link rel="stylesheet" type="text/css" href="./mw/site.styles.css">
<link rel="stylesheet" type="text/css" href="./mw/noscript.css">
<link rel="stylesheet" type="text/css" href="./footer.css">
<link rel="stylesheet" type="text/css" href="./vector-2022.css">
</head>
<body class="skin--responsive skin-vector skin-vector-search-vue mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Byte rootpage-Byte skin-vector-2022 action-view">
<div class="mw-page-container">
<div class="mw-page-container-inner">
<div class="mw-content-container">
<main id="content" class="mw-body">
<header class="mw-body-header vector-page-titlebar">
<h1 id="firstHeading" class="firstHeading mw-first-heading">
<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Byte</span></span>
</h1>
</header>
<a id="top"></a>
<div id="bodyContent" class="vector-body ve-init-mw-desktopArticleTarget-targetContainer" aria-labelledby="firstHeading" data-mw-ve-target-container="">
<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr">
<style data-mw-deduplicate="TemplateStyles:r1236090951">
/* start https://en.wikipedia.org/ */
.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}
/* end https://en.wikipedia.org/ */
</style><div role="note" class="hatnote navigation-not-searchable">This article is about the unit of information. For other uses, see <a href="Byte_(disambiguation)" class="mw-disambig" title="Byte (disambiguation)">Byte (disambiguation)</a>.</div>
<style data-mw-deduplicate="TemplateStyles:r1295905060">
/* start https://en.wikipedia.org/ */
.mw-parser-output .infobox-subbox{padding:0;border:none;margin:-3px;width:auto;min-width:100%;font-size:100%;clear:none;float:none;background-color:transparent}.mw-parser-output .infobox-3cols-child{margin:auto}.mw-parser-output .infobox .navbar{font-size:100%}@media screen{html.skin-theme-clientpref-night .mw-parser-output .infobox-full-data:not(.notheme)>div:not(.notheme)[style]{background:#1f1f23!important;color:#f8f9fa}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .infobox-full-data:not(.notheme)>div:not(.notheme)[style]{background:#1f1f23!important;color:#f8f9fa}}@media(min-width:640px){body.skin--responsive .mw-parser-output .infobox-table{display:table!important}body.skin--responsive .mw-parser-output .infobox-table>caption{display:table-caption!important}body.skin--responsive .mw-parser-output .infobox-table>tbody{display:table-row-group}body.skin--responsive .mw-parser-output .infobox-table th,body.skin--responsive .mw-parser-output .infobox-table td{padding-left:inherit;padding-right:inherit}}
/* end https://en.wikipedia.org/ */
</style><table class="infobox ib-unit"><tbody><tr><th colspan="2" class="infobox-above">byte</th></tr><tr><th scope="row" class="infobox-label"><a href="System_of_units_of_measurement" title="System of units of measurement">Unit system</a></th><td class="infobox-data">unit derived from <a href="Bit" title="Bit">bit</a></td></tr><tr><th scope="row" class="infobox-label">Unit of</th><td class="infobox-data">digital information, data size</td></tr><tr><th scope="row" class="infobox-label">Symbol</th><td class="infobox-data">B, <a href="Octet_(computing)" title="Octet (computing)">o</a> (when 8 bits)</td></tr></tbody></table><style data-mw-deduplicate="TemplateStyles:r1236303919">
/* start https://en.wikipedia.org/ */
@media screen{html.skin-theme-clientpref-night .mw-parser-output .infobox-has-images-with-white-backgrounds img{background:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .infobox-has-images-with-white-backgrounds img{background:white}}
/* end https://en.wikipedia.org/ */
</style>
<p>
</p><p>The <b>byte</b> is a <a href="Units_of_information" title="Units of information">unit of digital information</a> that most commonly consists of eight <a href="Bit" title="Bit">bits</a>. Historically, the byte was the number of bits used to encode a single <a href="Character_(computing)" title="Character (computing)">character</a> of text in a computer<sup id="cite_ref-Buchholz_1962_1-0" class="reference"><a href="#cite_note-Buchholz_1962-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Bemer_1959_2-0" class="reference"><a href="#cite_note-Bemer_1959-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> and for this reason it is the smallest <a href="Address_space" title="Address space">addressable</a> unit of <a href="Computer_memory" title="Computer memory">memory</a> in many <a href="Computer_architecture" title="Computer architecture">computer architectures</a>. To disambiguate arbitrarily sized bytes from the common <a href="8-bit_computing" title="8-bit computing">8-bit</a> definition, <a href="Computer_network" title="Computer network">network</a> protocol documents such as the <a href="Internet_Protocol" title="Internet Protocol">Internet Protocol</a> (<style data-mw-deduplicate="TemplateStyles:r1238218222">
/* start https://en.wikipedia.org/ */
.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}
/* end https://en.wikipedia.org/ */
</style><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc791">791</a>) refer to an 8-bit byte as an <a href="Octet_(computing)" title="Octet (computing)">octet</a>.<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> Those bits in an octet are usually counted with numbering from 0 to 7 or 7 to 0 depending on the <a href="Bit_numbering" title="Bit numbering">bit endianness</a>.
</p><p>The size of the byte has historically been <a href="Computer_hardware" title="Computer hardware">hardware</a>-dependent and no definitive standards existed that mandated the size. Sizes from 1 to 48 bits have been used.<sup id="cite_ref-Buchholz_1956_1_4-0" class="reference"><a href="#cite_note-Buchholz_1956_1-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-CDC_1965_3600_5-0" class="reference"><a href="#cite_note-CDC_1965_3600-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Rao_1989_6-0" class="reference"><a href="#cite_note-Rao_1989-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Tafel_1971_7-0" class="reference"><a href="#cite_note-Tafel_1971-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> The <a href="Six-bit_character_code" title="Six-bit character code">six-bit character code</a> was an often-used implementation in early encoding systems, and computers using six-bit and nine-bit bytes were common in the 1960s. These systems often had <a href="Word_(computer_architecture)" title="Word (computer architecture)">memory words</a> of 12, 18, 24, 30, 36, 48, or 60 bits, corresponding to 2, 3, 4, 5, 6, 8, or 10 six-bit bytes, and persisted, in legacy systems, into the twenty-first century. In this era, bit groupings in the instruction stream were often referred to as <i><a href="Syllable_(computing)" title="Syllable (computing)">syllables</a></i><sup id="cite_ref-8" class="reference"><a href="#cite_note-8"><span class="cite-bracket">[</span>a<span class="cite-bracket">]</span></a></sup> or <i>slab</i>, before the term <i>byte</i> became common.
</p><p>The modern <a href="De_facto_standard" title="De facto standard"><i>de facto</i> standard</a> of eight bits, as documented in ISO/IEC 2382-1:1993, is a convenient <a href="Power_of_two" title="Power of two">power of two</a> permitting the <a href="Binary_number" title="Binary number">binary-encoded</a> values 0 through 255 for one byte, as 2 to the power of 8 is 256.<sup id="cite_ref-ISO_IEC_2382-1_1993_9-0" class="reference"><a href="#cite_note-ISO_IEC_2382-1_1993-9"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> The international standard <a href="IEC_80000-13" class="mw-redirect" title="IEC 80000-13">IEC 80000-13</a> codified this common meaning. Many types of applications use information representable in eight or fewer bits and processor designers commonly optimize for this usage. The popularity of major commercial computing architectures has aided in the ubiquitous acceptance of the 8-bit byte.<sup id="cite_ref-CHM_1964_10-0" class="reference"><a href="#cite_note-CHM_1964-10"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> Modern architectures typically use 32- or 64-bit words, built of four or eight bytes, respectively.
</p><p>The unit symbol for the byte was designated as the upper-case letter B by the <a href="International_Electrotechnical_Commission" title="International Electrotechnical Commission">International Electrotechnical Commission</a> (IEC) and <a href="Institute_of_Electrical_and_Electronics_Engineers" title="Institute of Electrical and Electronics Engineers">Institute of Electrical and Electronics Engineers</a> (IEEE).<sup id="cite_ref-MIXF_11-0" class="reference"><a href="#cite_note-MIXF-11"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup> Internationally, the unit <i><a href="Octet_(computing)" title="Octet (computing)">octet</a></i> explicitly defines a sequence of eight bits, eliminating the potential ambiguity of the term "byte".<sup id="cite_ref-TCPIP_12-0" class="reference"><a href="#cite_note-TCPIP-12"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-ISO_2382-4_13-0" class="reference"><a href="#cite_note-ISO_2382-4-13"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup> The symbol for octet, 'o', also conveniently eliminates the ambiguity in the symbol 'B' between byte and <a href="Decibel" title="Decibel">bel</a>.
</p>
<meta property="mw:PageProp/toc">
<div class="mw-heading mw-heading2"><h2 id="Etymology_and_history">Etymology and history </h2></div>
<p>The term <i>byte</i> was coined by <a href="Werner_Buchholz" title="Werner Buchholz">Werner Buchholz</a> in June 1956,<sup id="cite_ref-Buchholz_1956_1_4-1" class="reference"><a href="#cite_note-Buchholz_1956_1-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Buchholz_1977_14-0" class="reference"><a href="#cite_note-Buchholz_1977-14"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Timeline_1956_15-0" class="reference"><a href="#cite_note-Timeline_1956-15"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-16" class="reference"><a href="#cite_note-16"><span class="cite-bracket">[</span>b<span class="cite-bracket">]</span></a></sup> during the early design phase for the <a href="IBM_7030" class="mw-redirect" title="IBM 7030">IBM Stretch</a><sup id="cite_ref-Buchholz_1956_2_17-0" class="reference"><a href="#cite_note-Buchholz_1956_2-17"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Buchholz_1956_3_18-0" class="reference"><a href="#cite_note-Buchholz_1956_3-18"><span class="cite-bracket">[</span>16<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Buchholz_1962_1-1" class="reference"><a href="#cite_note-Buchholz_1962-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Buchholz_1977_14-1" class="reference"><a href="#cite_note-Buchholz_1977-14"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Timeline_1956_15-1" class="reference"><a href="#cite_note-Timeline_1956-15"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-ESR_19-0" class="reference"><a href="#cite_note-ESR-19"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Bemer_2000_20-0" class="reference"><a href="#cite_note-Bemer_2000-20"><span class="cite-bracket">[</span>18<span class="cite-bracket">]</span></a></sup> computer, which had addressing to the bit and variable field length (VFL) instructions with a byte size encoded in the instruction.<sup id="cite_ref-Buchholz_1977_14-2" class="reference"><a href="#cite_note-Buchholz_1977-14"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup> It is a deliberate respelling of <i><a href="Bite" class="mw-redirect" title="Bite">bite</a></i> to avoid accidental mutation to <i><a href="Bit" title="Bit">bit</a></i>.<sup id="cite_ref-Buchholz_1962_1-2" class="reference"><a href="#cite_note-Buchholz_1962-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Buchholz_1977_14-3" class="reference"><a href="#cite_note-Buchholz_1977-14"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Blaauw_1959_21-0" class="reference"><a href="#cite_note-Blaauw_1959-21"><span class="cite-bracket">[</span>19<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-22" class="reference"><a href="#cite_note-22"><span class="cite-bracket">[</span>c<span class="cite-bracket">]</span></a></sup>
</p><p>Another origin of <i>byte</i> for bit groups smaller than a computer's word size, and in particular groups of <a href="Nibble_(computing)" class="mw-redirect" title="Nibble (computing)">four bits</a>, is on record by Louis G. Dooley, who claimed he coined the term while working with <a href="Jules_Schwartz" title="Jules Schwartz">Jules Schwartz</a> and Dick Beeler on an air defense system called <a href="Experimental_SAGE_Subsector" title="Experimental SAGE Subsector">SAGE</a> at <a href="MIT_Lincoln_Laboratory" title="MIT Lincoln Laboratory">MIT Lincoln Laboratory</a> in 1956 or 1957, which was jointly developed by <a href="Rand_Corporation" class="mw-redirect" title="Rand Corporation">Rand</a>, MIT, and IBM.<sup id="cite_ref-Dooley_1995_Byte_23-0" class="reference"><a href="#cite_note-Dooley_1995_Byte-23"><span class="cite-bracket">[</span>20<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Ram_Byte_24-0" class="reference"><a href="#cite_note-Ram_Byte-24"><span class="cite-bracket">[</span>21<span class="cite-bracket">]</span></a></sup> Later on, Schwartz's language <a href="JOVIAL" title="JOVIAL">JOVIAL</a> actually used the term, but the author recalled vaguely that it was derived from <a href="AN/FSQ-31" class="mw-redirect" title="AN/FSQ-31">AN/FSQ-31</a>.<sup id="cite_ref-Schwartz_Brooks_ACM_25-0" class="reference"><a href="#cite_note-Schwartz_Brooks_ACM-25"><span class="cite-bracket">[</span>22<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Ram_Byte_24-1" class="reference"><a href="#cite_note-Ram_Byte-24"><span class="cite-bracket">[</span>21<span class="cite-bracket">]</span></a></sup>
</p><p>Early computers used a variety of four-bit <a href="Binary-coded_decimal" title="Binary-coded decimal">binary-coded decimal</a> (BCD) representations and the <a href="Sixbit" class="mw-redirect" title="Sixbit">six-bit</a> codes for printable graphic patterns common in the <a href="U.S._Army" class="mw-redirect" title="U.S. Army">U.S. Army</a> (<a href="FIELDATA" class="mw-redirect" title="FIELDATA">FIELDATA</a>) and <a href="United_States_Navy" title="United States Navy">Navy</a>. These representations included alphanumeric characters and special graphical symbols. These sets were expanded in 1963 to seven bits of coding, called the <a href="American_Standard_Code_for_Information_Interchange" class="mw-redirect" title="American Standard Code for Information Interchange">American Standard Code for Information Interchange</a> (ASCII) as the <a href="Federal_Information_Processing_Standard" class="mw-redirect" title="Federal Information Processing Standard">Federal Information Processing Standard</a>, which replaced the incompatible teleprinter codes in use by different branches of the U.S. government and universities during the 1960s. ASCII included the distinction of upper- and lowercase alphabets and a set of <a href="Control_character" title="Control character">control characters</a> to facilitate the transmission of written language as well as printing device functions, such as page advance and line feed, and the physical or logical control of data flow over the transmission media.<sup id="cite_ref-Bemer_2000_20-1" class="reference"><a href="#cite_note-Bemer_2000-20"><span class="cite-bracket">[</span>18<span class="cite-bracket">]</span></a></sup> During the early 1960s, while also active in ASCII standardization, IBM simultaneously introduced in its product line of <a href="System/360" class="mw-redirect" title="System/360">System/360</a> the eight-bit <a href="Extended_Binary_Coded_Decimal_Interchange_Code" class="mw-redirect" title="Extended Binary Coded Decimal Interchange Code">Extended Binary Coded Decimal Interchange Code</a> (EBCDIC), an expansion of their <a href="Six-bit_binary-coded_decimal" class="mw-redirect" title="Six-bit binary-coded decimal">six-bit binary-coded decimal</a> (BCDIC) representations<sup id="cite_ref-26" class="reference"><a href="#cite_note-26"><span class="cite-bracket">[</span>d<span class="cite-bracket">]</span></a></sup> used in earlier card punches.<sup id="cite_ref-ibm.com_27-0" class="reference"><a href="#cite_note-ibm.com-27"><span class="cite-bracket">[</span>23<span class="cite-bracket">]</span></a></sup>
The prominence of the System/360 led to the ubiquitous adoption of the eight-bit storage size,<sup id="cite_ref-Bemer_2000_20-2" class="reference"><a href="#cite_note-Bemer_2000-20"><span class="cite-bracket">[</span>18<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Buchholz_1956_3_18-1" class="reference"><a href="#cite_note-Buchholz_1956_3-18"><span class="cite-bracket">[</span>16<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Buchholz_1977_14-4" class="reference"><a href="#cite_note-Buchholz_1977-14"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup> while in detail the EBCDIC and ASCII encoding schemes are different.
</p><p>In the early 1960s, <a href="AT%26T" title="AT&T">AT&T</a> introduced <a href="Digital_telephony" class="mw-redirect" title="Digital telephony">digital telephony</a> on long-distance <a href="Trunk_line" class="mw-redirect" title="Trunk line">trunk lines</a>. These used the eight-bit <a href="%CE%9C-law_algorithm" title="Μ-law algorithm">μ-law encoding</a>. This large investment promised to reduce transmission costs for eight-bit data.
</p><p>In Volume 1 of <i><a href="The_Art_of_Computer_Programming" title="The Art of Computer Programming">The Art of Computer Programming</a></i> (first published in 1968), <a href="Donald_Knuth" title="Donald Knuth">Donald Knuth</a> uses <i>byte</i> in his hypothetical <a href="MIX_(abstract_machine)" title="MIX (abstract machine)">MIX</a> computer to denote a unit which "contains an <i>unspecified</i> amount of information ... capable of holding at least 64 distinct values ... <i>at most</i> 100 distinct values. On a binary computer a byte must therefore be composed of six bits".<sup id="cite_ref-Knuth-1_28-0" class="reference"><a href="#cite_note-Knuth-1-28"><span class="cite-bracket">[</span>24<span class="cite-bracket">]</span></a></sup> He notes that "Since 1975 or so, the word <i>byte</i> has come to mean a sequence of precisely eight binary digits...When we speak of bytes in connection with MIX we shall confine ourselves to the former sense of the word, harking back to the days when bytes were not yet standardized."<sup id="cite_ref-Knuth-1_28-1" class="reference"><a href="#cite_note-Knuth-1-28"><span class="cite-bracket">[</span>24<span class="cite-bracket">]</span></a></sup>
</p><p>The development of <a href="Eight-bit" class="mw-redirect" title="Eight-bit">eight-bit</a> <a href="Microprocessor" title="Microprocessor">microprocessors</a> in the 1970s popularized this storage size. Microprocessors such as the <a href="Intel_8080" title="Intel 8080">Intel 8080</a>, the direct predecessor of the <a href="Intel_8086" title="Intel 8086">8086</a>, could also perform a small number of operations on the <a href="4bit" class="mw-redirect" title="4bit">four-bit</a> pairs in a byte, such as the decimal-add-adjust (DAA) instruction. A four-bit quantity is often called a <a href="Nibble" title="Nibble">nibble</a>, also <i>nybble</i>, which is conveniently represented by a single <a href="Hexadecimal" title="Hexadecimal">hexadecimal</a> digit.
</p><p>The term <i><a href="Octet_(computing)" title="Octet (computing)">octet</a></i> unambiguously specifies a size of eight bits.<sup id="cite_ref-Bemer_2000_20-3" class="reference"><a href="#cite_note-Bemer_2000-20"><span class="cite-bracket">[</span>18<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-ISO_2382-4_13-1" class="reference"><a href="#cite_note-ISO_2382-4-13"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup> It is used extensively in <a href="Protocol_(computing)" class="mw-redirect" title="Protocol (computing)">protocol</a> definitions.
</p><p>Historically, the term <i>octad</i> or <i>octade</i> was used to denote eight bits as well at least in Western Europe;<sup id="cite_ref-Williams_1969_29-0" class="reference"><a href="#cite_note-Williams_1969-29"><span class="cite-bracket">[</span>25<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Philips_1971_30-0" class="reference"><a href="#cite_note-Philips_1971-30"><span class="cite-bracket">[</span>26<span class="cite-bracket">]</span></a></sup> however, this usage is no longer common. The exact origin of the term is unclear, but it can be found in British, Dutch, and German sources of the 1960s and 1970s, and throughout the documentation of <a href="Philips" title="Philips">Philips</a> mainframe computers.
</p>
<div class="mw-heading mw-heading2"><h2 id="Unit_symbol">Unit symbol</h2></div>
<p>The unit symbol for the byte is specified in <a href="IEC_80000-13" class="mw-redirect" title="IEC 80000-13">IEC 80000-13</a>, <a href="IEEE_1541" title="IEEE 1541">IEEE 1541</a> and the Metric Interchange Format<sup id="cite_ref-MIXF_11-1" class="reference"><a href="#cite_note-MIXF-11"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup> as the upper-case character B.
</p><p>In the <a href="International_System_of_Quantities" title="International System of Quantities">International System of Quantities</a> (ISQ), B is also the symbol of the <i><a href="Bel_(acoustics)" class="mw-redirect" title="Bel (acoustics)">bel</a></i>, a unit of logarithmic power ratio named after <a href="Alexander_Graham_Bell" title="Alexander Graham Bell">Alexander Graham Bell</a>, creating a conflict with the IEC specification. However, little danger of confusion exists, because the bel is a rarely used unit. It is used primarily in its decadic fraction, the <a href="Decibel" title="Decibel">decibel</a> (dB), for <a href="Signal_strength" class="mw-redirect" title="Signal strength">signal strength</a> and <a href="Sound_pressure_level" class="mw-redirect" title="Sound pressure level">sound pressure level</a> measurements, while a unit for one-tenth of a byte, the decibyte, and other fractions, are only used in derived units, such as transmission rates.
</p><p>The lowercase letter o for <a href="Octet_(computing)" title="Octet (computing)">octet</a> is defined as the symbol for octet in IEC 80000-13 and is commonly used in languages such as <a href="French_language" title="French language">French</a><sup id="cite_ref-IEC_Binary_31-0" class="reference"><a href="#cite_note-IEC_Binary-31"><span class="cite-bracket">[</span>27<span class="cite-bracket">]</span></a></sup> and <a href="Romanian_language" title="Romanian language">Romanian</a>, and is also combined with metric prefixes for multiples, for example ko and Mo.
</p>
<div class="mw-heading mw-heading2"><h2 id="Multiple-byte_units">Multiple-byte units</h2></div>
<div role="note" class="hatnote navigation-not-searchable">"EiB" and "Exabyte" redirect here. For the company, see <a href="Exabyte_Corporation" title="Exabyte Corporation">Exabyte Corporation</a>. For other uses, see <a href="EIB_(disambiguation)" class="mw-redirect mw-disambig" title="EIB (disambiguation)">EIB (disambiguation)</a>.</div>
<div role="note" class="hatnote navigation-not-searchable">"Zettabytes" redirects here. For the fictional band "The Zetta Bytes", see <a href="Pixel_Perfect" title="Pixel Perfect">Pixel Perfect</a>.</div>
<div role="note" class="hatnote navigation-not-searchable">Several terms redirect here. For other uses, see <a href="Yottabyte_(disambiguation)" class="mw-disambig" title="Yottabyte (disambiguation)">Yottabyte (disambiguation)</a>, <a href="KIB_(disambiguation)" class="mw-redirect mw-disambig" title="KIB (disambiguation)">KIB (disambiguation)</a>, <a href="MIB_(disambiguation)" class="mw-redirect mw-disambig" title="MIB (disambiguation)">MIB (disambiguation)</a>, <a href="GIB_(disambiguation)" class="mw-redirect mw-disambig" title="GIB (disambiguation)">GIB (disambiguation)</a>, <a href="TIB_(disambiguation)" class="mw-redirect mw-disambig" title="TIB (disambiguation)">TIB (disambiguation)</a>, <a href="PIB_(disambiguation)" class="mw-redirect mw-disambig" title="PIB (disambiguation)">PIB (disambiguation)</a>, <a href="Zib_(disambiguation)" class="mw-redirect mw-disambig" title="Zib (disambiguation)">Zib (disambiguation)</a>, and <a href="RIB_(disambiguation)" class="mw-redirect mw-disambig" title="RIB (disambiguation)">RIB (disambiguation)</a>.</div>
<table style="text-align: left; float:right; clear:right; margin-left:1em; border:1px #aaa solid; font-size:88%;">
<tbody><tr>
<th colspan="2" style="background-color:#ccf;padding-left:3em;padding-right:1em;text-align:center;"><style data-mw-deduplicate="TemplateStyles:r1129693374">
/* start https://en.wikipedia.org/ */
.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}
/* end https://en.wikipedia.org/ */
</style><style data-mw-deduplicate="TemplateStyles:r1239400231">
/* start https://en.wikipedia.org/ */
.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}
/* end https://en.wikipedia.org/ */
</style> <span style="font-size:120%;"><a class="mw-selflink-fragment" href="#Multiple-byte_units">Multiple-byte units</a></span>
</th></tr>
<tr>
<td style="padding:0">
<table style="border:1px #aaa solid">
<tbody><tr>
<th colspan="3" style="background-color:#ccf; text-align:center;"><a href="Decimal" title="Decimal">Decimal</a>
</th></tr>
<tr>
<th style="background-color:#ddf; text-align:center; padding:0;">Value
</th>
<th colspan="2" style="background-color:#ddf; text-align:center; padding:0"><a href="Metric_prefix" title="Metric prefix">Metric</a>
</th></tr>
<tr>
<td>1000
</td>
<td>kB</td>
<td><a href="Kilobyte" title="Kilobyte">kilobyte</a>
</td></tr>
<tr>
<td>1000<sup>2</sup>
</td>
<td>MB</td>
<td><a href="Megabyte" title="Megabyte">megabyte</a>
</td></tr>
<tr>
<td>1000<sup>3</sup>
</td>
<td>GB</td>
<td><a href="Gigabyte" title="Gigabyte">gigabyte</a>
</td></tr>
<tr>
<td>1000<sup>4</sup>
</td>
<td>TB</td>
<td>terabyte
</td></tr>
<tr>
<td>1000<sup>5</sup>
</td>
<td>PB</td>
<td>petabyte
</td></tr>
<tr>
<td>1000<sup>6</sup>
</td>
<td>EB</td>
<td>exabyte
</td></tr>
<tr>
<td>1000<sup>7</sup>
</td>
<td>ZB</td>
<td>zettabyte
</td></tr>
<tr>
<td>1000<sup>8</sup>
</td>
<td>YB</td>
<td>yottabyte
</td></tr>
<tr>
<td>1000<sup>9</sup>
</td>
<td>RB</td>
<td>ronnabyte
</td></tr>
<tr>
<td>1000<sup>10</sup>
</td>
<td>QB</td>
<td>quettabyte
</td></tr></tbody></table>
</td>
<td style="padding:0">
<table style="border: 1px #aaa solid">
<tbody><tr>
<th colspan="5" style="background-color:#ccf; text-align:center;"><a href="Binary_prefix" title="Binary prefix">Binary</a>
</th></tr>
<tr>
<th style="background-color:#ddf; text-align:center; padding:0;">Value
</th>
<th colspan="2" style="background-color:#ddf; text-align:center; padding:0"><a href="IEC_80000-13" class="mw-redirect" title="IEC 80000-13">IEC</a>
</th>
<th colspan="2" style="background-color:#ddf; text-align:center; padding:0"><a href="JEDEC_memory_standards#Unit_prefixes_for_semiconductor_storage_capacity" title="JEDEC memory standards"><style data-mw-deduplicate="TemplateStyles:r1038841319">
/* start https://en.wikipedia.org/ */
'"`UNIQ--templatestyles-0000003F-QINU`"'
/* end https://en.wikipedia.org/ */
</style><span class="rt-commentedText tooltip tooltip-dotted" title="Size of directly addressable memory is historically denoted with KB, MB, etc., to mean binary multiples.">Memory</span></a>
</th></tr>
<tr>
<td>1024
</td>
<td>KiB</td>
<td>kibibyte
</td>
<td>KB</td>
<td>kilobyte
</td></tr>
<tr>
<td>1024<sup>2</sup>
</td>
<td>MiB</td>
<td>mebibyte
</td>
<td>MB</td>
<td>megabyte
</td></tr>
<tr>
<td>1024<sup>3</sup>
</td>
<td>GiB</td>
<td>gibibyte
</td>
<td>GB</td>
<td>gigabyte
</td></tr>
<tr>
<td>1024<sup>4</sup>
</td>
<td>TiB</td>
<td>tebibyte
</td>
<td>TB</td>
<td>terabyte
</td></tr>
<tr>
<td>1024<sup>5</sup>
</td>
<td>PiB</td>
<td>pebibyte
</td>
<td colspan="2" style="text-align: center;">—
</td></tr>
<tr>
<td>1024<sup>6</sup>
</td>
<td>EiB</td>
<td>exbibyte
</td>
<td colspan="2" style="text-align: center;">—
</td></tr>
<tr>
<td>1024<sup>7</sup>
</td>
<td>ZiB</td>
<td>zebibyte
</td>
<td colspan="2" style="text-align: center;">—
</td></tr>
<tr>
<td>1024<sup>8</sup>
</td>
<td>YiB</td>
<td>yobibyte
</td>
<td colspan="2" style="text-align: center;">—
</td></tr>
<tr>
<td>1024<sup>9</sup>
</td>
<td>RiB</td>
<td>robibyte
</td>
<td colspan="2" style="text-align: center;">—
</td></tr>
<tr>
<td>1024<sup>10</sup>
</td>
<td>QiB</td>
<td>quebibyte
</td>
<td colspan="2" style="text-align: center;">—
</td></tr></tbody></table>
</td></tr>
<tr>
<td colspan="5" style="background-color:#ddf;text-align:center;"><a href="Orders_of_magnitude_(data)" title="Orders of magnitude (data)">Orders of magnitude of data</a>
</td></tr></tbody></table>
<p>More than one system exists to define <a href="Unit_multiple" class="mw-redirect" title="Unit multiple">unit multiples</a> based on the byte. Some systems are based on <a href="Power_of_10" title="Power of 10">powers of 10</a>, following the <a href="International_System_of_Units" title="International System of Units">International System of Units</a> (SI), which defines for example the prefix <i><a href="Kilo-" title="Kilo-">kilo</a></i> as 1000 (10<sup>3</sup>); other systems are based on <a href="Power_of_two" title="Power of two">powers of two</a>. Nomenclature for these systems has led to confusion. Systems based on powers of 10 use standard <a href="SI_prefix" class="mw-redirect" title="SI prefix">SI prefixes</a> (<i><a href="Kilo-" title="Kilo-">kilo</a></i>, <i><a href="Mega-" title="Mega-">mega</a></i>, <i><a href="Giga-" title="Giga-">giga</a></i>, ...) and their corresponding symbols (k, M, G, ...). Systems based on powers of 2, however, might use binary prefixes (<i>kibi</i>, <i>mebi</i>, <i>gibi</i>, ...) and their corresponding symbols (Ki, Mi, Gi, ...) or they might use the prefixes K, M, and G, creating ambiguity when the prefixes M or G are used.
</p><p>While the difference between the decimal and binary interpretations is relatively small for the kilobyte (about 2% smaller than the kibibyte), the systems deviate increasingly as units grow larger (the relative deviation grows by 2.4% for each three orders of magnitude). For example, a power-of-10-based terabyte is about 9% smaller than power-of-2-based tebibyte.
</p>
<div class="mw-heading mw-heading3"><h3 id="Units_based_on_powers_of_10">Units based on powers of 10</h3></div>
<p>Definition of prefixes using powers of 10—in which 1 <i>kilobyte</i> (symbol kB) is defined to equal 1,000 bytes—is recommended by the International Electrotechnical Commission (IEC).<sup id="cite_ref-NIST_32-0" class="reference"><a href="#cite_note-NIST-32"><span class="cite-bracket">[</span>28<span class="cite-bracket">]</span></a></sup> The IEC standard defines eight such multiples, up to 1 yottabyte (YB), equal to 1000<sup>8</sup> bytes.<sup id="cite_ref-33" class="reference"><a href="#cite_note-33"><span class="cite-bracket">[</span>29<span class="cite-bracket">]</span></a></sup> The additional prefixes <i>ronna-</i> for 1000<sup>9</sup> and <i>quetta-</i> for 1000<sup>10</sup> were adopted by the <a href="International_Bureau_of_Weights_and_Measures" title="International Bureau of Weights and Measures">International Bureau of Weights and Measures</a> (BIPM) in 2022.<sup id="cite_ref-34" class="reference"><a href="#cite_note-34"><span class="cite-bracket">[</span>30<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-35" class="reference"><a href="#cite_note-35"><span class="cite-bracket">[</span>31<span class="cite-bracket">]</span></a></sup>
</p><p>This definition is most commonly used for <a href="Data-rate_units" title="Data-rate units">data-rate units</a> in <a href="Computer_network" title="Computer network">computer networks</a>, internal bus, hard drive and flash media transfer speeds, and for the capacities of most <a href="Storage_media" class="mw-redirect" title="Storage media">storage media</a>, particularly <a href="Hard_drive" class="mw-redirect" title="Hard drive">hard drives</a>,<sup id="cite_ref-36" class="reference"><a href="#cite_note-36"><span class="cite-bracket">[</span>32<span class="cite-bracket">]</span></a></sup> <a href="Flash_memory" title="Flash memory">flash</a>-based storage,<sup id="cite_ref-37" class="reference"><a href="#cite_note-37"><span class="cite-bracket">[</span>33<span class="cite-bracket">]</span></a></sup> and <a href="DVD" title="DVD">DVDs</a>. <a href="Operating_system" title="Operating system">Operating systems</a> that use this definition include <a href="MacOS" title="MacOS">macOS</a>,<sup id="cite_ref-apple_38-0" class="reference"><a href="#cite_note-apple-38"><span class="cite-bracket">[</span>34<span class="cite-bracket">]</span></a></sup> <a href="IOS" title="IOS">iOS</a>,<sup id="cite_ref-apple_38-1" class="reference"><a href="#cite_note-apple-38"><span class="cite-bracket">[</span>34<span class="cite-bracket">]</span></a></sup> <a href="Ubuntu" title="Ubuntu">Ubuntu</a>,<sup id="cite_ref-39" class="reference"><a href="#cite_note-39"><span class="cite-bracket">[</span>35<span class="cite-bracket">]</span></a></sup> and <a href="Debian" title="Debian">Debian</a>.<sup id="cite_ref-40" class="reference"><a href="#cite_note-40"><span class="cite-bracket">[</span>36<span class="cite-bracket">]</span></a></sup> It is also consistent with the other uses of the <a href="SI_prefix" class="mw-redirect" title="SI prefix">SI prefixes</a> in computing, such as <a href="Hertz#Computers" title="Hertz">CPU clock speeds</a> or <a href="FLOPS" class="mw-redirect" title="FLOPS">measures of performance</a>.
</p><p>The IBM System 360 and the related disk and tape systems set the byte at 8 bits and documented capacities in decimal units.<sup id="cite_ref-41" class="reference"><a href="#cite_note-41"><span class="cite-bracket">[</span>37<span class="cite-bracket">]</span></a></sup> The early 8-, 5.25- and 3.5-inch floppies gave capacities in multiples of 1024, using "KB" rather than the more accurate "KiB". The later, larger, 8-, 5.25- and 3.5-inch floppies gave capacities in a hybrid notation, i.e., multiples of 1024,000, using <span class="nowrap">"KB" = 1024 B</span> and <span class="nowrap">"MB" = 1024,000 B.</span>
Early 5.25-inch disks used decimal even though they used 128-byte and 256-byte sectors.<sup id="cite_ref-42" class="reference"><a href="#cite_note-42"><span class="cite-bracket">[</span>38<span class="cite-bracket">]</span></a></sup> Hard disks used mostly 256-byte and then 512-byte before 4096-byte blocks became standard.<sup id="cite_ref-43" class="reference"><a href="#cite_note-43"><span class="cite-bracket">[</span>39<span class="cite-bracket">]</span></a></sup> RAM was always sold in powers of 2.
</p>
<div class="mw-heading mw-heading3"><h3 id="Units_based_on_powers_of_2">Units based on powers of 2</h3></div>
<p>A system of units based on <a href="Powers_of_2" class="mw-redirect" title="Powers of 2">powers of 2</a> in which 1 kibibyte (KiB) is equal to 1,024 (i.e., 2<sup>10</sup>) bytes is defined by international standard IEC 80000-13 and is supported by national and international standards bodies (<a href="BIPM" class="mw-redirect" title="BIPM">BIPM</a>, <a href="International_Electrotechnical_Commission" title="International Electrotechnical Commission">IEC</a>, <a href="NIST" class="mw-redirect" title="NIST">NIST</a>). The IEC standard defines eight such multiples, up to 1 yobibyte (YiB), equal to 1024<sup>8</sup> bytes. The natural binary counterparts to <i>ronna-</i> and <i>quetta-</i> were given in a consultation paper of the International Committee for Weights and Measures' Consultative Committee for Units (CCU) as <i>robi-</i> (Ri, 1024<sup>9</sup>) and <i>quebi-</i> (Qi, 1024<sup>10</sup>), but have not yet been adopted by the IEC or ISO.<sup id="cite_ref-44" class="reference"><a href="#cite_note-44"><span class="cite-bracket">[</span>40<span class="cite-bracket">]</span></a></sup>
</p><p>An alternative system of nomenclature for the same units (referred to here as the <i>customary convention</i>), in which 1 <i>kilobyte</i> (KB) is equal to 1,024 bytes,<sup id="cite_ref-45" class="reference"><a href="#cite_note-45"><span class="cite-bracket">[</span>41<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-46" class="reference"><a href="#cite_note-46"><span class="cite-bracket">[</span>42<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-47" class="reference"><a href="#cite_note-47"><span class="cite-bracket">[</span>43<span class="cite-bracket">]</span></a></sup> 1 <i>megabyte</i> (MB) is equal to 1024<sup>2</sup> bytes and 1 <i>gigabyte</i> (GB) is equal to 1024<sup>3</sup> bytes is mentioned by a 1990s <a href="JEDEC" title="JEDEC">JEDEC</a> standard. Only the first three multiples (up to GB) are mentioned by the JEDEC standard, which makes no mention of TB and larger. While confusing and incorrect,<sup id="cite_ref-48" class="reference"><a href="#cite_note-48"><span class="cite-bracket">[</span>44<span class="cite-bracket">]</span></a></sup> the customary convention is used by the <a href="Microsoft_Windows" title="Microsoft Windows">Microsoft Windows</a> operating system<sup id="cite_ref-auto_49-0" class="reference"><a href="#cite_note-auto-49"><span class="cite-bracket">[</span>45<span class="cite-bracket">]</span></a></sup> and <a href="Random-access_memory" title="Random-access memory">random-access memory</a> capacity, such as main memory and <a href="CPU_cache" title="CPU cache">CPU cache</a> size, and in marketing and billing by telecommunication companies, such as <a href="Vodafone" title="Vodafone">Vodafone</a>,<sup id="cite_ref-50" class="reference"><a href="#cite_note-50"><span class="cite-bracket">[</span>46<span class="cite-bracket">]</span></a></sup> <a href="AT%26T" title="AT&T">AT&T</a>,<sup id="cite_ref-51" class="reference"><a href="#cite_note-51"><span class="cite-bracket">[</span>47<span class="cite-bracket">]</span></a></sup> <a href="Orange_S.A." class="mw-redirect" title="Orange S.A.">Orange</a><sup id="cite_ref-52" class="reference"><a href="#cite_note-52"><span class="cite-bracket">[</span>48<span class="cite-bracket">]</span></a></sup> and <a href="Telstra" title="Telstra">Telstra</a>.<sup id="cite_ref-53" class="reference"><a href="#cite_note-53"><span class="cite-bracket">[</span>49<span class="cite-bracket">]</span></a></sup>
</p><p>For <a href="Computer_data_storage" title="Computer data storage">storage</a> capacity, the customary convention was used by macOS and iOS through Mac OS X 10.5 Leopard and iOS 10, after which they switched to units based on powers of 10.<sup id="cite_ref-apple_38-2" class="reference"><a href="#cite_note-apple-38"><span class="cite-bracket">[</span>34<span class="cite-bracket">]</span></a></sup>
</p>
<div class="mw-heading mw-heading3"><h3 id="Parochial_units">Parochial units</h3></div>
<p>Various computer vendors have coined terms for data of various sizes, sometimes with different sizes for the same term even within a single vendor. These terms include <i>double word</i>, <i>half word</i>, <i>long word</i>, <i>quad word</i>, <i>slab</i>, <i>superword</i> and <i>syllable</i>. There are also informal terms. e.g., <i>half byte</i> and <i>nybble</i> for 4 bits, <i>octal K</i> for 1000<sub>8</sub>.
</p>
<div class="mw-heading mw-heading3"><h3 id="History_of_the_conflicting_definitions">History of the conflicting definitions</h3></div>
<style data-mw-deduplicate="TemplateStyles:r1244412712">
/* start https://en.wikipedia.org/ */
.mw-parser-output .templatequote{overflow:hidden;margin:1em 0;padding:0 32px}.mw-parser-output .templatequotecite{line-height:1.5em;text-align:left;margin-top:0}@media(min-width:500px){.mw-parser-output .templatequotecite{padding-left:1.6em}}
/* end https://en.wikipedia.org/ */
</style><blockquote class="templatequote"><p>When I see a disk advertised as having a capacity of one megabyte, what is this telling me? There are three plausible answers, and I wonder if anybody knows which one is correct ... Now this is not a really vital issue, as there is just under 5% difference between the smallest and largest alternatives. Nevertheless, it would [be] nice to know what the standard measure is, or if there is one.</p></blockquote><div class="templatequotecite"><p style="display: inline; padding-left: 2.3em;">— Allan D. Pratt of <i>Small Computers in Libraries</i>, 1982<sup id="cite_ref-pratt19820412_54-0" class="reference"><a href="#cite_note-pratt19820412-54"><span class="cite-bracket">[</span>50<span class="cite-bracket">]</span></a></sup></p></div>
<p>Contemporary<sup id="cite_ref-55" class="reference"><a href="#cite_note-55"><span class="cite-bracket">[</span>e<span class="cite-bracket">]</span></a></sup> computer memory has a <a href="Binary_addressing" class="mw-redirect" title="Binary addressing">binary architecture</a> making a definition of memory units based on powers of 2 most practical. The use of the metric prefix <i>kilo</i> for binary multiples arose as a convenience, because <span class="nowrap">1024</span> is approximately <span class="nowrap">1000</span>.<sup id="cite_ref-IEC_Binary_31-1" class="reference"><a href="#cite_note-IEC_Binary-31"><span class="cite-bracket">[</span>27<span class="cite-bracket">]</span></a></sup> This definition was popular in early decades of <a href="Personal_computing" class="mw-redirect" title="Personal computing">personal computing</a>, with products like the <a href="Tandon_Corporation" title="Tandon Corporation">Tandon</a> 5<style data-mw-deduplicate="TemplateStyles:r1154941027">
/* start https://en.wikipedia.org/ */
.mw-parser-output .frac{white-space:nowrap}.mw-parser-output .frac .num,.mw-parser-output .frac .den{font-size:80%;line-height:0;vertical-align:super}.mw-parser-output .frac .den{vertical-align:sub}.mw-parser-output .sr-only{border:0;clip:rect(0,0,0,0);clip-path:polygon(0px 0px,0px 0px,0px 0px);height:1px;margin:-1px;overflow:hidden;padding:0;position:absolute;width:1px}
/* end https://en.wikipedia.org/ */
</style><span class="frac"><span class="num">1</span>⁄<span class="den">4</span></span>-inch <a href="Double_density" class="mw-redirect" title="Double density">DD</a> floppy format (holding <span class="nowrap">368<span style="margin-left:.25em;">640</span></span> bytes) being advertised as "360 KB", following the <span class="nowrap">1024</span>-byte convention. It was not universal, however. The <a href="Shugart_Associates" title="Shugart Associates">Shugart</a> SA-400 5<span class="frac"><span class="num">1</span>⁄<span class="den">4</span></span>-inch <a href="Floppy_disk" title="Floppy disk">floppy disk</a> held 109,375 bytes unformatted,<sup id="cite_ref-56" class="reference"><a href="#cite_note-56"><span class="cite-bracket">[</span>51<span class="cite-bracket">]</span></a></sup> and was advertised as "110 Kbyte", using the 1000 convention.<sup id="cite_ref-57" class="reference"><a href="#cite_note-57"><span class="cite-bracket">[</span>52<span class="cite-bracket">]</span></a></sup> Likewise, the 8-inch <a href="Digital_Equipment_Corporation" title="Digital Equipment Corporation">DEC</a> RX01 floppy (1975) held <span class="nowrap">256<span style="margin-left:.25em;">256</span></span> bytes formatted, and was advertised as "256k".<sup id="cite_ref-58" class="reference"><a href="#cite_note-58"><span class="cite-bracket">[</span>53<span class="cite-bracket">]</span></a></sup> Some devices were advertised using a <i>mixture</i> of the two definitions: most notably, floppy disks advertised as "1.44 MB" have an actual capacity of <span class="nowrap">1440 KiB</span>, the equivalent of 1.47 MB or 1.41 MiB.
</p><p>In 1995, the <a href="International_Union_of_Pure_and_Applied_Chemistry" title="International Union of Pure and Applied Chemistry">International Union of Pure and Applied Chemistry</a>'s (IUPAC) Interdivisional Committee on Nomenclature and Symbols attempted to resolve this ambiguity by proposing a set of <a href="Binary_prefixes" class="mw-redirect" title="Binary prefixes">binary prefixes</a> for the powers of 1024, including kibi (kilobinary), mebi (megabinary), and gibi (gigabinary).<sup id="cite_ref-59" class="reference"><a href="#cite_note-59"><span class="cite-bracket">[</span>54<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-60" class="reference"><a href="#cite_note-60"><span class="cite-bracket">[</span>55<span class="cite-bracket">]</span></a></sup>
</p><p>In December 1998, the <a href="International_Electrotechnical_Commission" title="International Electrotechnical Commission">IEC</a> addressed such multiple usages and definitions by adopting the IUPAC's proposed prefixes (kibi, mebi, gibi, etc.) to unambiguously denote powers of 1024.<sup id="cite_ref-61" class="reference"><a href="#cite_note-61"><span class="cite-bracket">[</span>56<span class="cite-bracket">]</span></a></sup> Thus one kibibyte (1 KiB) is 1024<sup>1</sup> bytes = 1024 bytes, one mebibyte (1 MiB) is 1024<sup>2</sup> bytes = <span class="nowrap">1<span style="margin-left:.25em;">048</span><span style="margin-left:.25em;">576</span></span> bytes, and so on.
</p><p>In 1999, <a href="Donald_Knuth" title="Donald Knuth">Donald Knuth</a> suggested calling the kibibyte a "large kilobyte" (<i>KKB</i>).<sup id="cite_ref-kilobyte_62-0" class="reference"><a href="#cite_note-kilobyte-62"><span class="cite-bracket">[</span>57<span class="cite-bracket">]</span></a></sup>
</p>
<div class="mw-heading mw-heading3"><h3 id="Modern_standard_definitions">Modern standard definitions</h3></div>
<p>The IEC adopted the IUPAC proposal and published the standard in January 1999.<sup id="cite_ref-63" class="reference"><a href="#cite_note-63"><span class="cite-bracket">[</span>58<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-64" class="reference"><a href="#cite_note-64"><span class="cite-bracket">[</span>59<span class="cite-bracket">]</span></a></sup> The IEC prefixes are part of the <a href="IEC_80000-13" class="mw-redirect" title="IEC 80000-13">International System of Quantities</a>. The IEC further specified that the kilobyte should only be used to refer to <span class="nowrap">1000</span> bytes.<sup id="cite_ref-65" class="reference"><a href="#cite_note-65"><span class="cite-bracket">[</span>60<span class="cite-bracket">]</span></a></sup>
</p>
<div class="mw-heading mw-heading3"><h3 id="Lawsuits_over_definition">Lawsuits over definition</h3></div>
<p>Lawsuits arising from alleged consumer confusion over the binary and decimal definitions of multiples of the byte have generally ended in favor of the manufacturers, with courts holding that the legal definition of gigabyte or GB is 1 GB = <span class="nowrap">1<span style="margin-left:.25em;">000</span><span style="margin-left:.25em;">000</span><span style="margin-left:.25em;">000</span></span> (10<sup>9</sup>) bytes (the decimal definition), rather than the binary definition (2<sup>30</sup>, i.e., <span class="nowrap">1<span style="margin-left:.25em;">073</span><span style="margin-left:.25em;">741</span><span style="margin-left:.25em;">824</span></span>). Specifically, the United States District Court for the Northern District of California held that "the U.S. Congress has deemed the decimal definition of gigabyte to be the 'preferred' one for the purposes of 'U.S. trade and commerce' [...] The California Legislature has likewise adopted the decimal system for all 'transactions in this state.<span style="padding-right:.15em;">'</span>"<sup id="cite_ref-Order_Granting_Motion_to_Dismiss_66-0" class="reference"><a href="#cite_note-Order_Granting_Motion_to_Dismiss-66"><span class="cite-bracket">[</span>61<span class="cite-bracket">]</span></a></sup>
</p><p>Earlier lawsuits had ended in settlement with no court ruling on the question, such as a lawsuit against drive manufacturer <a href="Western_Digital" title="Western Digital">Western Digital</a>.<sup id="cite_ref-WesternDigital_67-0" class="reference"><a href="#cite_note-WesternDigital-67"><span class="cite-bracket">[</span>62<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Baskin-2006-02-01_68-0" class="reference"><a href="#cite_note-Baskin-2006-02-01-68"><span class="cite-bracket">[</span>63<span class="cite-bracket">]</span></a></sup> Western Digital settled the challenge and added explicit disclaimers to products that the usable capacity may differ from the advertised capacity.<sup id="cite_ref-WesternDigital_67-1" class="reference"><a href="#cite_note-WesternDigital-67"><span class="cite-bracket">[</span>62<span class="cite-bracket">]</span></a></sup> Seagate was sued on similar grounds and also settled.<sup id="cite_ref-WesternDigital_67-2" class="reference"><a href="#cite_note-WesternDigital-67"><span class="cite-bracket">[</span>62<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Seagate_69-0" class="reference"><a href="#cite_note-Seagate-69"><span class="cite-bracket">[</span>64<span class="cite-bracket">]</span></a></sup>
</p>
<div class="mw-heading mw-heading3"><h3 id="Practical_examples">Practical examples</h3></div>
<table class="wikitable sortable">
<tbody><tr>
<th width="55">Unit
</th>
<th width="450" class="unsortable">Approximate equivalent
</th></tr>
<tr>
<td rowspan="1">bit
</td>
<td>a <a href="Boolean_data_type" title="Boolean data type">Boolean</a> variable indicating true (1) or false (0)
</td></tr>
<tr>
<td rowspan="1">byte
</td>
<td>a <a href="Basic_Latin_(Unicode_block)" title="Basic Latin (Unicode block)">basic Latin</a> character.
</td></tr>
<tr>
<td rowspan="2">kilobyte
</td>
<td>text of "<a href="Jabberwocky" title="Jabberwocky">Jabberwocky</a>"
</td></tr>
<tr>
<td>a typical <a href="Favicon" title="Favicon">favicon</a>
</td></tr>
<tr>
<td rowspan="1">megabyte
</td>
<td>text of <i><a href="Harry_Potter_and_the_Goblet_of_Fire" title="Harry Potter and the Goblet of Fire">Harry Potter and the Goblet of Fire</a></i><sup id="cite_ref-70" class="reference"><a href="#cite_note-70"><span class="cite-bracket">[</span>65<span class="cite-bracket">]</span></a></sup>
</td></tr>
<tr>
<td rowspan="2">gigabyte
</td>
<td>about half an hour of <a href="DVD-Video" title="DVD-Video">DVD</a> video<sup id="cite_ref-71" class="reference"><a href="#cite_note-71"><span class="cite-bracket">[</span>66<span class="cite-bracket">]</span></a></sup>
</td></tr>
<tr>
<td><a href="CD" class="mw-redirect" title="CD">CD</a>-quality uncompressed audio of <i><a href="The_Lamb_Lies_Down_on_Broadway" title="The Lamb Lies Down on Broadway">The Lamb Lies Down on Broadway</a></i>
</td></tr>
<tr>
<td rowspan="2">terabyte
</td>
<td>the largest consumer hard drive in 2007<sup id="cite_ref-Hitachi1st_72-0" class="reference"><a href="#cite_note-Hitachi1st-72"><span class="cite-bracket">[</span>67<span class="cite-bracket">]</span></a></sup>
</td></tr>
<tr>
<td>75 hours of video, encoded at 30 Mbit/second
</td></tr>
<tr>
<td>petabyte
</td>
<td><span class="nowrap">2000</span> years of <a href="MP3" title="MP3">MP3</a>-encoded music<sup id="cite_ref-computerweekly.com_73-0" class="reference"><a href="#cite_note-computerweekly.com-73"><span class="cite-bracket">[</span>68<span class="cite-bracket">]</span></a></sup>
</td></tr>
<tr>
<td rowspan="1">exabyte
</td>
<td>global monthly <a href="Internet_traffic" title="Internet traffic">Internet traffic</a> in 2004<sup id="cite_ref-74" class="reference"><a href="#cite_note-74"><span class="cite-bracket">[</span>69<span class="cite-bracket">]</span></a></sup>
</td></tr>
<tr>
<td>zettabyte
</td>
<td>global yearly Internet traffic in 2016 (known as the <i><a href="Zettabyte_Era" title="Zettabyte Era">Zettabyte Era</a></i>)<sup id="cite_ref-75" class="reference"><a href="#cite_note-75"><span class="cite-bracket">[</span>70<span class="cite-bracket">]</span></a></sup>
</td></tr></tbody></table>
<div class="mw-heading mw-heading2"><h2 id="Common_uses">Common uses</h2></div>
<p>Many <a href="Programming_language" title="Programming language">programming languages</a> define the <a href="Data_type" title="Data type">data type</a> <i>byte</i>.
</p><p>The <a href="C_(programming_language)" title="C (programming language)">C</a> and <a href="C%2B%2B" title="C++">C++</a> programming languages define <i>byte</i> as an "addressable unit of data storage large enough to hold any member of the basic character set of the execution environment" (clause 3.6 of the C standard). The C standard requires that the integral data type <i><a href="Signedness" title="Signedness">unsigned</a> char</i> must hold at least 256 different values, and is represented by at least eight bits (clause 5.2.4.2.1). Various implementations of C and C++ reserve 8, 9, 16, 32, or 36 bits for the storage of a byte.<sup id="cite_ref-Cline_Bytes_76-0" class="reference"><a href="#cite_note-Cline_Bytes-76"><span class="cite-bracket">[</span>71<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Klein_2008_77-0" class="reference"><a href="#cite_note-Klein_2008-77"><span class="cite-bracket">[</span>72<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-78" class="reference"><a href="#cite_note-78"><span class="cite-bracket">[</span>f<span class="cite-bracket">]</span></a></sup> In addition, the C and C++ standards require that there be no gaps between two bytes. This means every bit in memory is part of a byte.<sup id="cite_ref-Cline_FAQ_79-0" class="reference"><a href="#cite_note-Cline_FAQ-79"><span class="cite-bracket">[</span>73<span class="cite-bracket">]</span></a></sup>
</p><p><a href="Java_(programming_language)" title="Java (programming language)">Java's</a> primitive data type <i>byte</i> is defined as eight bits. It is a signed data type, holding values from −128 to 127.
</p><p><a href=".NET" title=".NET">.NET</a> programming languages, such as <a href="C_Sharp_(programming_language)" title="C Sharp (programming language)">C#</a>, define <i>byte</i> as an unsigned type, and the <i>sbyte</i> as a signed data type, holding values from 0 to 255, and <a href="Two's_complement" title="Two's complement">−128 to 127</a>, respectively.
</p><p>In data transmission systems, the byte is used as a contiguous sequence of bits in a serial data stream, representing the smallest distinguished unit of data. For <a href="Asynchronous_communication" title="Asynchronous communication">asynchronous communication</a> a full transmission unit usually additionally includes a start bit, 1 or 2 stop bits, and possibly a <a href="Parity_bit" title="Parity bit">parity bit</a>, and thus its size may vary from seven to twelve bits for five to eight bits of actual data.<sup id="cite_ref-NWU_80-0" class="reference"><a href="#cite_note-NWU-80"><span class="cite-bracket">[</span>74<span class="cite-bracket">]</span></a></sup> For <a href="Synchronous_communication" class="mw-redirect" title="Synchronous communication">synchronous communication</a> the error checking usually uses bytes at the end of a <a href="Frame_(networking)" title="Frame (networking)">frame</a>.
</p>
<div class="mw-heading mw-heading2"><h2 id="See_also">See also</h2></div>
<ul><li><a href="Data" title="Data">Data</a></li>
<li><a href="Data_hierarchy" title="Data hierarchy">Data hierarchy</a></li>
<li><a href="Nibble" title="Nibble">Nibble</a></li>
<li><a href="Octet_(computing)" title="Octet (computing)">Octet (computing)</a></li>
<li><a href="Primitive_data_type" title="Primitive data type">Primitive data type</a></li>
<li><a href="Tryte" class="mw-redirect" title="Tryte">Tryte</a></li>
<li><a href="Word_(computer_architecture)" title="Word (computer architecture)">Word (computer architecture)</a></li></ul>
<div class="mw-heading mw-heading2"><h2 id="Notes">Notes</h2></div>
<div style="list-style-type: lower-alpha">
<ol class="references">
<li id="cite_note-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-8">^</a></b></span> <span class="reference-text">The term syllable was used for bytes containing instructions or constituents of instructions, not for data bytes.</span>
</li>
<li id="cite_note-16"><span class="mw-cite-backlink"><b><a href="#cite_ref-16">^</a></b></span> <span class="reference-text">Many sources erroneously indicate a birthday of the term <i>byte</i> in July 1956, but <a href="Werner_Buchholz" title="Werner Buchholz">Werner Buchholz</a> claimed that the term would have been coined in <a href="#Buchholz-1977">June 1956</a>. In fact, the <a href="#Buchholz-1956-1">earliest document</a> supporting this dates from 1956-06-11. Buchholz stated that the transition to 8-bit bytes was conceived in <a href="#Buchholz-1977">August 1956</a>, but the earliest document found using this notion dates from <a href="#Buchholz-1956-3">September 1956</a>.</span>
</li>
<li id="cite_note-22"><span class="mw-cite-backlink"><b><a href="#cite_ref-22">^</a></b></span> <span class="reference-text">Some later machines, e.g., <a href="Burroughs_B1700" title="Burroughs B1700">Burroughs B1700</a>, <a href="CDC_3600" class="mw-redirect" title="CDC 3600">CDC 3600</a>, DEC PDP-6, <a href="DEC_PDP-10" class="mw-redirect" title="DEC PDP-10">DEC PDP-10</a> had the ability to operate on arbitrary bytes no larger than the word size.</span>
</li>
<li id="cite_note-26"><span class="mw-cite-backlink"><b><a href="#cite_ref-26">^</a></b></span> <span class="reference-text">There was more than one BCD code page.</span>
</li>
<li id="cite_note-55"><span class="mw-cite-backlink"><b><a href="#cite_ref-55">^</a></b></span> <span class="reference-text">Through the 1970s there were machines with <a href="Decimal_computer" title="Decimal computer">decimal</a> architectures.</span>
</li>
<li id="cite_note-78"><span class="mw-cite-backlink"><b><a href="#cite_ref-78">^</a></b></span> <span class="reference-text">The actual number of bits in a particular implementation is documented as <code>CHAR_BIT</code> as implemented in the file <a href="Limits.h" class="mw-redirect" title="Limits.h">limits.h</a>.</span>
</li>
</ol>
</div>
<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>
<style data-mw-deduplicate="TemplateStyles:r1239543626">
/* start https://en.wikipedia.org/ */
.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}
/* end https://en.wikipedia.org/ */
</style><div class="reflist">
<div class="mw-references-wrap mw-references-columns"><ol class="references">
<li id="cite_note-Buchholz_1962-1"><span class="mw-cite-backlink">^ <a href="#cite_ref-Buchholz_1962_1-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Buchholz_1962_1-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-Buchholz_1962_1-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text">
<cite id="CITEREFBlaauwBrooks,_Jr.Buchholz1962" class="citation cs2"><a href="Gerrit_Anne_Blaauw" class="mw-redirect" title="Gerrit Anne Blaauw">Blaauw, Gerrit Anne</a>; <a href="Frederick_Phillips_Brooks%2C_Jr." class="mw-redirect" title="Frederick Phillips Brooks, Jr.">Brooks, Jr., Frederick Phillips</a>; <a href="Werner_Buchholz" title="Werner Buchholz">Buchholz, Werner</a> (1962), <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170403014651/http://archive.computerhistory.org/resources/text/IBM/Stretch/pdfs/Buchholz_102636426.pdf">"Chapter 4: Natural Data Units"</a> <span class="cs1-format">(PDF)</span>, in <a href="Werner_Buchholz" title="Werner Buchholz">Buchholz, Werner</a> (ed.), <i>Planning a Computer System - Project Stretch</i>, <a href="McGraw-Hill_Book_Company%2C_Inc." class="mw-redirect" title="McGraw-Hill Book Company, Inc.">McGraw-Hill Book Company, Inc.</a> / The Maple Press Company, York, PA., pp. <span class="nowrap">39–</span>40, <a href="LCCN_(identifier)" class="mw-redirect" title="LCCN (identifier)">LCCN</a> <a rel="nofollow" class="external text" href="https://lccn.loc.gov/61-10466">61-10466</a>, archived from <a rel="nofollow" class="external text" href="http://archive.computerhistory.org/resources/text/IBM/Stretch/pdfs/Buchholz_102636426.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2017-04-03<span class="reference-accessdate">, retrieved <span class="nowrap">2017-04-03</span></span></cite>
<blockquote class="templatequote"><div class="poem">
<p> Terms used here to describe the structure imposed by the machine design, in addition to <i><a href="Bit" title="Bit">bit</a></i>, are listed below.<br>
<i>Byte</i> denotes a group of bits used to encode a character, or the number of bits transmitted in parallel to and from input-output units. A term other than <i><a href="Character_(computing)" title="Character (computing)">character</a></i> is used here because a given character may be represented in different applications by more than one code, and different codes may use different numbers of bits (i.e., different byte sizes). In input-output transmission the grouping of bits may be completely arbitrary and have no relation to actual characters. (The term is coined from <i><a href="Bite" class="mw-redirect" title="Bite">bite</a></i>, but respelled to avoid accidental mutation to <i>bit</i>.)<br>
A <i><a href="Word_(unit)" class="mw-redirect" title="Word (unit)">word</a></i> consists of the number of data bits transmitted in parallel from or to memory in one memory cycle. <a href="Word_size" class="mw-redirect" title="Word size">Word size</a> is thus defined as a structural property of the memory. (The term <i><a href="Catena_(unit)" class="mw-redirect" title="Catena (unit)">catena</a></i> was coined for this purpose by the designers of the <a href="Groupe_Bull" title="Groupe Bull">Bull</a> <a href="Bull_Gamma_60" title="Bull Gamma 60">GAMMA 60</a> computer.)<br>
<i><a href="Block_(data_storage)" title="Block (data storage)">Block</a></i> refers to the number of words transmitted to or from an input-output unit in response to a single input-output instruction. Block size is a structural property of an input-output unit; it may have been fixed by the design or left to be varied by the program.
</p>
</div></blockquote>
<p class="mw-empty-elt">
</p>
</span></li>
<li id="cite_note-Bemer_1959-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-Bemer_1959_2-0">^</a></b></span> <span class="reference-text">
<cite id="CITEREFBemer1959" class="citation cs2"><a href="Robert_William_Bemer" class="mw-redirect" title="Robert William Bemer">Bemer, Robert William</a> (1959), "A proposal for a generalized card code of 256 characters", <i><a href="Communications_of_the_ACM" title="Communications of the ACM">Communications of the ACM</a></i>, <b>2</b> (9): <span class="nowrap">19–</span>23, <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F368424.368435">10.1145/368424.368435</a></span>, <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:36115735">36115735</a></cite>
</span>
</li>
<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text">
<cite id="CITEREFPostel1981" class="citation cs1">Postel, J. (September 1981). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc791#page-43"><i>Internet Protocol DARPA INTERNET PROGRAM PROTOCOL SPECIFICATION</i></a>. p. 43. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC0791">10.17487/RFC0791</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc791">791</a><span class="reference-accessdate">. Retrieved <span class="nowrap">28 August</span> 2020</span>. <q>octet An eight bit byte.</q></cite></span>
</li>
<li id="cite_note-Buchholz_1956_1-4"><span class="mw-cite-backlink">^ <a href="#cite_ref-Buchholz_1956_1_4-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Buchholz_1956_1_4-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">
<cite id="CITEREFBuchholz1956" class="citation book cs1"><a href="Werner_Buchholz" title="Werner Buchholz">Buchholz, Werner</a> (1956-06-11). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170404152534/http://archive.computerhistory.org/resources/text/IBM/Stretch/pdfs/06-07/102632284.pdf">"7. The Shift Matrix"</a> <span class="cs1-format">(PDF)</span>. <i>The Link System</i>. <a href="IBM" title="IBM">IBM</a>. pp. <span class="nowrap">5–</span>6. <a href="IBM_Stretch" class="mw-redirect" title="IBM Stretch">Stretch</a> Memo No. 39G. Archived from <a rel="nofollow" class="external text" href="http://archive.computerhistory.org/resources/text/IBM/Stretch/pdfs/06-07/102632284.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2017-04-04<span class="reference-accessdate">. Retrieved <span class="nowrap">2016-04-04</span></span>.</cite>
<blockquote class="templatequote"><div class="poem">
<p> [...] Most important, from the point of view of editing, will be the ability to handle any characters or digits, from 1 to 6 bits long.<br>
Figure 2 shows the Shift Matrix to be used to convert a 60-bit <a href="Word_(computer_architecture)" title="Word (computer architecture)">word</a>, coming from Memory in parallel, into <a href="Character_(computing)" title="Character (computing)">characters</a>, or 'bytes' as we have called them, to be sent to the <a href="Serial_adder" class="mw-redirect" title="Serial adder">Adder</a> serially. The 60 bits are dumped into <a href="Magnetic_core" title="Magnetic core">magnetic cores</a> on six different levels. Thus, if a 1 comes out of position 9, it appears in all six cores underneath. Pulsing any diagonal line will send the six bits stored along that line to the Adder. The Adder may accept all or only some of the bits.<br>
Assume that it is desired to operate on 4 bit <a href="Decimal_digit" class="mw-redirect" title="Decimal digit">decimal digits</a>, starting at the right. The 0-diagonal is pulsed first, sending out the six bits 0 to 5, of which the Adder accepts only the first four (0-3). Bits 4 and 5 are ignored. Next, the 4 diagonal is pulsed. This sends out bits 4 to 9, of which the last two are again ignored, and so on.<br>
It is just as easy to use all six bits in <a href="Alphanumeric" class="mw-redirect" title="Alphanumeric">alphanumeric</a> work, or to handle bytes of only one bit for logical analysis, or to offset the bytes by any number of bits. All this can be done by pulling the appropriate shift diagonals. An analogous matrix arrangement is used to change from serial to parallel operation at the output of the adder. [...]
</p>
</div></blockquote>
<p class="mw-empty-elt">
</p>
</span></li>
<li id="cite_note-CDC_1965_3600-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-CDC_1965_3600_5-0">^</a></b></span> <span class="reference-text">
<cite class="citation book cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20170405154001/http://bitsavers.informatik.uni-stuttgart.de/pdf/cdc/3x00/48bit/60021300K_3600_SysRef_Oct66.pdf"><i>3600 Computer System - Reference Manual</i></a> <span class="cs1-format">(PDF)</span>. K. St. Paul, Minnesota, US: <a href="Control_Data_Corporation" title="Control Data Corporation">Control Data Corporation</a> (CDC). 1966-10-11 [1965]. 60021300. Archived from <a rel="nofollow" class="external text" href="http://bitsavers.org/pdf/cdc/3x00/48bit/60021300K_3600_SysRef_Oct66.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2017-04-05<span class="reference-accessdate">. Retrieved <span class="nowrap">2017-04-05</span></span>. <q>Byte - A partition of a computer word.</q></cite><br>
NB. Discusses 12-bit, 24-bit and 48-bit bytes.
</span>
</li>
<li id="cite_note-Rao_1989-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-Rao_1989_6-0">^</a></b></span> <span class="reference-text">
<cite id="CITEREFRaoFujiwara1989" class="citation book cs1">Rao, Thammavaram R. N.; Fujiwara, Eiji (1989). McCluskey, Edward J. (ed.). <a rel="nofollow" class="external text" href="https://archive.org/details/errorcontrolcodi00unse"><i>Error-Control Coding for Computer Systems</i></a>. Prentice Hall Series in Computer Engineering (1 ed.). Englewood Cliffs, NJ, US: <a href="Prentice_Hall" title="Prentice Hall">Prentice Hall</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-13-283953-9</bdi>. <a href="LCCN_(identifier)" class="mw-redirect" title="LCCN (identifier)">LCCN</a> <a rel="nofollow" class="external text" href="https://lccn.loc.gov/88-17892">88-17892</a>.</cite><br>
NB. Example of the usage of a code for "4-bit bytes".
</span>
</li>
<li id="cite_note-Tafel_1971-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-Tafel_1971_7-0">^</a></b></span> <span class="reference-text">
<cite id="CITEREFTafel1971" class="citation book cs1 cs1-prop-foreign-lang-source">Tafel, Hans Jörg (1971). <i>Einführung in die digitale Datenverarbeitung</i> [<i>Introduction to digital information processing</i>] (in German). Munich: <a href="Carl_Hanser_Verlag" title="Carl Hanser Verlag">Carl Hanser Verlag</a>. p. 300. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>3-446-10569-7</bdi>. <q>Byte = zusammengehörige Folge von i.a. neun Bits; davon sind acht Datenbits, das neunte ein Prüfbit</q></cite><br>
NB. Defines a byte as a group of typically 9 bits; 8 data bits plus 1 parity bit.
</span>
</li>
<li id="cite_note-ISO_IEC_2382-1_1993-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-ISO_IEC_2382-1_1993_9-0">^</a></b></span> <span class="reference-text">
<cite class="citation book cs1"><i>ISO/IEC 2382-1: 1993, Information technology - Vocabulary - Part 1: Fundamental terms</i>. 1993.</cite>
<blockquote class="templatequote"><div class="poem">
<p> byte:<br>
A string that consists of a number of bits, treated as a unit, and usually representing a character or a part of a character.<br>
NOTES:<br>
1 The number of bits in a byte is fixed for a given data processing system.<br>
2 The number of bits in a byte is usually 8.
</p>
</div></blockquote>
<p class="mw-empty-elt">
</p>
</span></li>
<li id="cite_note-CHM_1964-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-CHM_1964_10-0">^</a></b></span> <span class="reference-text">
<cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.computerhistory.org/internethistory/1960s/#1964">"Internet History of 1960s # 1964"</a>. <a href="Computer_History_Museum" title="Computer History Museum">Computer History Museum</a>. 2017 [2015]. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20220624184757/https://www.computerhistory.org/internethistory/1960s/#1964">Archived</a> from the original on 2022-06-24<span class="reference-accessdate">. Retrieved <span class="nowrap">2022-08-17</span></span>.</cite>
</span>
</li>
<li id="cite_note-MIXF-11"><span class="mw-cite-backlink">^ <a href="#cite_ref-MIXF_11-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-MIXF_11-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">
<cite id="CITEREFJaffer2011" class="citation web cs1">Jaffer, Aubrey (2011) [2008]. <a rel="nofollow" class="external text" href="https://people.csail.mit.edu/jaffer/MIXF/">"Metric-Interchange-Format"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170403121705/https://people.csail.mit.edu/jaffer/MIXF/">Archived</a> from the original on 2017-04-03<span class="reference-accessdate">. Retrieved <span class="nowrap">2017-04-03</span></span>.</cite>
</span>
</li>
<li id="cite_note-TCPIP-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-TCPIP_12-0">^</a></b></span> <span class="reference-text">
<cite id="CITEREFKozierok2005" class="citation web cs1">Kozierok, Charles M. (2005-09-20) [2001]. <a rel="nofollow" class="external text" href="http://www.tcpipguide.com/free/t_BinaryInformationandRepresentationBitsBytesNibbles-3.htm">"The TCP/IP Guide - Binary Information and Representation: Bits, Bytes, Nibbles, Octets and Characters - Byte versus Octet"</a>. 3.0. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170403122042/http://www.tcpipguide.com/free/t_BinaryInformationandRepresentationBitsBytesNibbles-3.htm">Archived</a> from the original on 2017-04-03<span class="reference-accessdate">. Retrieved <span class="nowrap">2017-04-03</span></span>.</cite>
</span>
</li>
<li id="cite_note-ISO_2382-4-13"><span class="mw-cite-backlink">^ <a href="#cite_ref-ISO_2382-4_13-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-ISO_2382-4_13-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">
<cite class="citation book cs1"><i>ISO 2382-4, Organization of data</i> (2 ed.). <q>byte, octet, 8-bit byte: A string that consists of eight bits.</q></cite>
</span>
</li>
<li id="cite_note-Buchholz_1977-14"><span class="mw-cite-backlink">^ <a href="#cite_ref-Buchholz_1977_14-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Buchholz_1977_14-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-Buchholz_1977_14-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-Buchholz_1977_14-3"><sup><i><b>d</b></i></sup></a> <a href="#cite_ref-Buchholz_1977_14-4"><sup><i><b>e</b></i></sup></a></span> <span class="reference-text">
<cite id="CITEREFBuchholz1977" class="citation journal cs1"><a href="Werner_Buchholz" title="Werner Buchholz">Buchholz, Werner</a> (February 1977). <a rel="nofollow" class="external text" href="https://archive.org/details/byte-magazine-1977-02/page/n145/mode/1up">"The Word "Byte" Comes of Age..."</a> <i><a href="Byte_Magazine" class="mw-redirect" title="Byte Magazine">Byte Magazine</a></i>. <b>2</b> (2): 144.</cite>
<blockquote class="templatequote"><div class="poem">
<p> <i>We received the following from W Buchholz, one of the individuals who was working on IBM's Project Stretch in the mid 1950s. His letter tells the story.</i><br>
<br>
Not being a regular reader of your magazine, I heard about the question in the November 1976 issue regarding the origin of the term "byte" from a colleague who knew that I had perpetrated this piece of jargon <i>[see page 77 of November 1976 BYTE, "Olde Englishe"]</i>. I searched my files and could not locate a birth certificate. But I am sure that "byte" is coming of age in 1977 with its 21st birthday.<br>
Many have assumed that byte, meaning 8 bits, originated with the IBM System/360, which spread such bytes far and wide in the mid-1960s. The editor is correct in pointing out that the term goes back to the earlier Stretch computer (but incorrect in that Stretch was the first, not the last, of IBM's second-generation transistorized computers to be developed).<br>
The first reference found in the files was contained in an internal memo written in June 1956 during the early days of developing <a href="IBM_Stretch" class="mw-redirect" title="IBM Stretch">Stretch</a>. A byte was described as consisting of any number of parallel bits from one to six. Thus a byte was assumed to have a length appropriate for the occasion. Its first use was in the context of the input-output equipment of the 1950s, which handled six bits at a time. The possibility of going to 8-bit bytes was considered in <a href="#Note-Dates">August 1956</a> and incorporated in the design of Stretch <a href="#Buchholz-1956-3">shortly thereafter</a>.<br>
The first published reference to the term occurred in 1959 in a paper '<a href="#Blaauw-1959">Processing Data in Bits and Pieces</a>' by <a href="Gerrit_Anne_Blaauw" class="mw-redirect" title="Gerrit Anne Blaauw">G A Blaauw</a>, <a href="Frederick_Phillips_Brooks%2C_Jr." class="mw-redirect" title="Frederick Phillips Brooks, Jr.">F P Brooks Jr</a> and <a href="Werner_Buchholz" title="Werner Buchholz">W Buchholz</a> in the <i><a href="IRE_Transactions_on_Electronic_Computers" class="mw-redirect" title="IRE Transactions on Electronic Computers">IRE Transactions on Electronic Computers</a></i>, June 1959, page 121. The notions of that paper were elaborated in <a href="#Buchholz-1962">Chapter 4 of <i>Planning a Computer System (Project Stretch)</i></a>, edited by W Buchholz, McGraw-Hill Book Company (1962). The rationale for coining the term was explained there on page 40 as follows:<br>
<span class="mw-poem-indented" style="display: inline-block; margin-inline-start: 2em;"> Byte <i>denotes a group of bits used to encode a character, or the number of bits transmitted in parallel to and from input-output units. A term other than</i> character <i>is used here because a given character may be represented in different applications by more than one code, and different codes may use different numbers of bits (ie, different byte sizes). In input-output transmission the grouping of bits may be completely arbitrary and have no relation to actual characters. (The term is coined from</i> <a href="Bite" class="mw-redirect" title="Bite">bite</a>, <i>but respelled to avoid accidental mutation to</i> bit.<i>)</i></span><br>
<a href="System/360" class="mw-redirect" title="System/360">System/360</a> took over many of the Stretch concepts, including the basic byte and word sizes, which are powers of 2. For economy, however, the byte size was fixed at the 8 bit maximum, and addressing at the bit level was replaced by byte addressing.<br>
Since then the term byte has generally meant 8 bits, and it has thus passed into the general vocabulary.<br>
Are there any other terms coined especially for the computer field which have found their way into general dictionaries of English language?
</p>
</div></blockquote>
<p class="mw-empty-elt">
</p>
</span></li>
<li id="cite_note-Timeline_1956-15"><span class="mw-cite-backlink">^ <a href="#cite_ref-Timeline_1956_15-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Timeline_1956_15-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">
<cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20160429212717/http://archive.computerhistory.org/resources/text/IBM/Stretch/102636400.txt">"Timeline of the IBM Stretch/Harvest era (1956-1961)"</a>. <a href="Computer_History_Museum" title="Computer History Museum">Computer History Museum</a>. June 1956. Archived from <a rel="nofollow" class="external text" href="http://archive.computerhistory.org/resources/text/IBM/Stretch/102636400.txt">the original</a> on 2016-04-29<span class="reference-accessdate">. Retrieved <span class="nowrap">2017-04-03</span></span>.</cite>
<blockquote class="templatequote"><div class="poem">
<p> 1956 Summer: <a href="Gerrit_Blaauw" title="Gerrit Blaauw">Gerrit Blaauw</a>, <a href="Fred_Brooks" title="Fred Brooks">Fred Brooks</a>, <a href="Werner_Buchholz" title="Werner Buchholz">Werner Buchholz</a>, <a href="John_Cocke_(computer_scientist)" title="John Cocke (computer scientist)">John Cocke</a> and Jim Pomerene join the <a href="IBM_Stretch" class="mw-redirect" title="IBM Stretch">Stretch</a> team. Lloyd Hunter provides <a href="Transistor" title="Transistor">transistor</a> leadership.<br>
1956 July [<i><a href="Sic" title="Sic">sic</a></i>]: In a report Werner Buchholz lists the advantages of a 64-bit word length for Stretch. It also supports <a href="NSA" class="mw-redirect" title="NSA">NSA</a>'s requirement for 8-bit bytes. Werner's term "Byte" first popularized in this memo.
</p>
</div></blockquote>
<p> NB. This timeline erroneously specifies the birth date of the term "byte" as <i><a href="#Note-Dates">July 1956</a></i>, while Buchholz actually used the term as early as <i><a href="#Buchholz-1956-1">June 1956</a></i>.
</p>
</span></li>
<li id="cite_note-Buchholz_1956_2-17"><span class="mw-cite-backlink"><b><a href="#cite_ref-Buchholz_1956_2_17-0">^</a></b></span> <span class="reference-text">
<cite id="CITEREFBuchholz1956" class="citation book cs1"><a href="Werner_Buchholz" title="Werner Buchholz">Buchholz, Werner</a> (1956-07-31). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170404160423/http://archive.computerhistory.org/resources/text/IBM/Stretch/pdfs/06-08/102632289.pdf">"5. Input-Output"</a> <span class="cs1-format">(PDF)</span>. <i>Memory Word Length</i>. <a href="IBM" title="IBM">IBM</a>. p. 2. <a href="IBM_Stretch" class="mw-redirect" title="IBM Stretch">Stretch</a> Memo No. 40. Archived from <a rel="nofollow" class="external text" href="http://archive.computerhistory.org/resources/text/IBM/Stretch/pdfs/06-08/102632289.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2017-04-04<span class="reference-accessdate">. Retrieved <span class="nowrap">2016-04-04</span></span>.</cite>
<blockquote class="templatequote"><div class="poem">
<p> [...] 60 is a multiple of 1, 2, 3, 4, 5, and 6. Hence bytes of length from 1 to 6 bits can be packed efficiently into a 60-bit <a href="Word_(computer_architecture)" title="Word (computer architecture)">word</a> without having to split a byte between one word and the next. If longer bytes were needed, 60 bits would, of course, no longer be ideal. With present applications, 1, 4, and 6 bits are the really important cases.<br>
With 64-bit words, it would often be necessary to make some compromises, such as leaving 4 bits unused in a word when dealing with 6-bit bytes at the input and output. However, the LINK Computer can be equipped to edit out these gaps and to permit handling of bytes which are split between words. [...]
</p>
</div></blockquote>
<p class="mw-empty-elt">
</p>
</span></li>
<li id="cite_note-Buchholz_1956_3-18"><span class="mw-cite-backlink">^ <a href="#cite_ref-Buchholz_1956_3_18-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Buchholz_1956_3_18-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">
<cite id="CITEREFBuchholz1956" class="citation book cs1"><a href="Werner_Buchholz" title="Werner Buchholz">Buchholz, Werner</a> (1956-09-19). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170404161611/http://archive.computerhistory.org/resources/text/IBM/Stretch/pdfs/06-08/102632292.pdf">"2. Input-Output Byte Size"</a> <span class="cs1-format">(PDF)</span>. <i>Memory Word Length and Indexing</i>. <a href="IBM" title="IBM">IBM</a>. p. 1. <a href="IBM_Stretch" class="mw-redirect" title="IBM Stretch">Stretch</a> Memo No. 45. Archived from <a rel="nofollow" class="external text" href="http://archive.computerhistory.org/resources/text/IBM/Stretch/pdfs/06-08/102632292.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2017-04-04<span class="reference-accessdate">. Retrieved <span class="nowrap">2016-04-04</span></span>.</cite>
<blockquote class="templatequote"><div class="poem">
<p> [...] The maximum input-output byte size for serial operation will now be 8 bits, not counting any error detection and correction bits. Thus, the Exchange will operate on an 8-bit byte basis, and any input-output units with less than 8 bits per byte will leave the remaining bits blank. The resultant gaps can be edited out later by programming [...]
</p>
</div></blockquote>
<p class="mw-empty-elt">
</p>
</span></li>
<li id="cite_note-ESR-19"><span class="mw-cite-backlink"><b><a href="#cite_ref-ESR_19-0">^</a></b></span> <span class="reference-text">
<cite id="CITEREFRaymond2017" class="citation web cs1"><a href="Eric_Steven_Raymond" class="mw-redirect" title="Eric Steven Raymond">Raymond, Eric Steven</a> (2017) [2003]. <a rel="nofollow" class="external text" href="http://catb.org/~esr/jargon/html/B/byte.html">"byte definition"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170403120304/http://catb.org/~esr/jargon/html/B/byte.html">Archived</a> from the original on 2017-04-03<span class="reference-accessdate">. Retrieved <span class="nowrap">2017-04-03</span></span>.</cite>
</span>
</li>
<li id="cite_note-Bemer_2000-20"><span class="mw-cite-backlink">^ <a href="#cite_ref-Bemer_2000_20-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Bemer_2000_20-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-Bemer_2000_20-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-Bemer_2000_20-3"><sup><i><b>d</b></i></sup></a></span> <span class="reference-text">
<cite id="CITEREFBemer2000" class="citation web cs1"><a href="Robert_William_Bemer" class="mw-redirect" title="Robert William Bemer">Bemer, Robert William</a> (2000-08-08). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170403130829/http://www.bobbemer.com/BYTE.HTM">"Why is a byte 8 bits? Or is it?"</a>. <i>Computer History Vignettes</i>. Archived from <a rel="nofollow" class="external text" href="http://www.bobbemer.com/BYTE.HTM">the original</a> on 2017-04-03<span class="reference-accessdate">. Retrieved <span class="nowrap">2017-04-03</span></span>.</cite>
<blockquote class="templatequote"><div class="poem">
<p>I came to work for <a href="IBM" title="IBM">IBM</a>, and saw all the confusion caused by the 64-character limitation. Especially when we started to think about word processing, which would require both upper and lower case.<br>
<i>Add 26 lower case letters to 47 existing, and one got 73 -- 9 more than 6 bits could represent.</i><br>
I even made a proposal (in view of <a href="IBM_Stretch" class="mw-redirect" title="IBM Stretch">STRETCH</a>, the very first computer I know of with an 8-bit byte) that would extend the number of <a href="Punch_card" class="mw-redirect" title="Punch card">punch card</a> character codes to 256 <a href="#Bemer_1959">[1]</a>.<br>
<i>Some folks took it seriously. I thought of it as a spoof.</i><br>
So some folks started thinking about 7-bit characters, but this was ridiculous. With IBM's STRETCH computer as background, handling 64-character words divisible into groups of 8 (I designed the character set for it, under the guidance of Dr. <a href="Werner_Buchholz" title="Werner Buchholz">Werner Buchholz</a>, the man who DID coin the term "byte" for an 8-bit grouping). [2] It seemed reasonable to make a universal 8-bit character set, handling up to 256. In those days my mantra was "powers of 2 are magic". And so the group I headed developed and justified such a proposal [3].<br>
<i>That was a little too much progress when presented to the standards group that was to formalize ASCII, so they stopped short for the moment with a 7-bit set, or else an 8-bit set with the upper half left for future work.</i><br>
The <a href="IBM_System_360" class="mw-redirect" title="IBM System 360">IBM 360</a> used 8-bit characters, although not ASCII directly. Thus Buchholz's "byte" caught on everywhere. I myself did not like the name for many reasons. The design had 8 bits moving around in parallel. But then came a new IBM part, with 9 bits for self-checking, both inside the CPU and in the <a href="Tape_drive" title="Tape drive">tape drives</a>. I exposed this 9-bit byte to the press in 1973. But long before that, when I headed software operations for <a href="Cie._Bull" class="mw-redirect" title="Cie. Bull">Cie. Bull</a> in France in 1965-66, I insisted that 'byte' be deprecated in favor of "<a href="Octet_(computing)" title="Octet (computing)">octet</a>".<br>
<i>You can notice that my preference then is now the preferred term.</i><br>
It is justified by new communications methods that can carry 16, 32, 64, and even 128 bits in parallel. But some foolish people now refer to a "16-bit byte" because of this parallel transfer, which is visible in the <a href="UNICODE" class="mw-redirect" title="UNICODE">UNICODE</a> set. I'm not sure, but maybe this should be called a "<a href="Hextet" title="Hextet">hextet</a>".<br>
<i>But you will notice that I am still correct. Powers of 2 are still magic!</i>
</p>
</div></blockquote>
<p class="mw-empty-elt">
</p>
</span></li>
<li id="cite_note-Blaauw_1959-21"><span class="mw-cite-backlink"><b><a href="#cite_ref-Blaauw_1959_21-0">^</a></b></span> <span class="reference-text">
<cite id="CITEREFBlaauwBrooks,_Jr.Buchholz1959" class="citation journal cs1"><a href="Gerrit_Anne_Blaauw" class="mw-redirect" title="Gerrit Anne Blaauw">Blaauw, Gerrit Anne</a>; <a href="Frederick_Phillips_Brooks%2C_Jr." class="mw-redirect" title="Frederick Phillips Brooks, Jr.">Brooks, Jr., Frederick Phillips</a>; <a href="Werner_Buchholz" title="Werner Buchholz">Buchholz, Werner</a> (June 1959). "Processing Data in Bits and Pieces". <i><a href="IRE_Transactions_on_Electronic_Computers" class="mw-redirect" title="IRE Transactions on Electronic Computers">IRE Transactions on Electronic Computers</a></i>: 121.</cite>
</span>
</li>
<li id="cite_note-Dooley_1995_Byte-23"><span class="mw-cite-backlink"><b><a href="#cite_ref-Dooley_1995_Byte_23-0">^</a></b></span> <span class="reference-text">
<cite id="CITEREFDooley1995" class="citation journal cs1">Dooley, Louis G. (February 1995). <a rel="nofollow" class="external text" href="https://web.archive.org/web/19961220122258/http://www.byte.com/art/9502/sec2/art12.htm">"Byte: The Word"</a>. <i><a href="BYTE" class="mw-redirect" title="BYTE">BYTE</a></i>. Ocala, FL, US. Archived from <a rel="nofollow" class="external text" href="http://www.byte.com/art/9502/sec2/art12.htm">the original</a> on 1996-12-20.</cite>
<blockquote class="templatequote"><div class="poem">
<p> The word byte was coined around 1956 to 1957 at <a href="MIT_Lincoln_Laboratory" title="MIT Lincoln Laboratory">MIT Lincoln Laboratories</a> within a project called <a href="Experimental_SAGE_Subsector" title="Experimental SAGE Subsector">SAGE</a> (the North American Air Defense System), which was jointly developed by <a href="Rand_Corporation" class="mw-redirect" title="Rand Corporation">Rand</a>, Lincoln Labs, and <a href="IBM" title="IBM">IBM</a>. In that era, computer memory structure was already defined in terms of <a href="Word_size_(computing)" class="mw-redirect" title="Word size (computing)">word size</a>. A word consisted of x number of <a href="Bit" title="Bit">bits</a>; a bit represented a binary notational position in a word. Operations typically operated on all the bits in the full word.<br>
We coined the word byte to refer to a logical set of bits less than a full word size. At that time, it was not defined specifically as x bits but typically referred to as a set of <a href="Nibble_(computing)" class="mw-redirect" title="Nibble (computing)">4 bits</a>, as that was the size of most of our coded data items. Shortly afterward, I went on to other responsibilities that removed me from SAGE. After having spent many years in Asia, I returned to the U.S. and was bemused to find out that the word byte was being used in the new microcomputer technology to refer to the basic addressable memory unit.
</p>
</div></blockquote>
<p class="mw-empty-elt">
</p>
</span></li>
<li id="cite_note-Ram_Byte-24"><span class="mw-cite-backlink">^ <a href="#cite_ref-Ram_Byte_24-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Ram_Byte_24-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">
<cite id="CITEREFRam2003" class="citation web cs1 cs1-prop-foreign-lang-source">Ram, Stefan (17 January 2003). <a rel="nofollow" class="external text" href="http://userpage.fu-berlin.de/~ram/pub/pub_jf47ht81Ht/code_byte_de">"Erklärung des Wortes "Byte" im Rahmen der Lehre binärer Codes"</a> (in German). Berlin, Germany: <a href="Freie_Universit%C3%A4t_Berlin" class="mw-redirect" title="Freie Universität Berlin">Freie Universität Berlin</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210610055304/http://userpage.fu-berlin.de/~ram/pub/pub_jf47ht81Ht/code_byte_de">Archived</a> from the original on 2021-06-10<span class="reference-accessdate">. Retrieved <span class="nowrap">2017-04-10</span></span>.</cite></span>
</li>
<li id="cite_note-Schwartz_Brooks_ACM-25"><span class="mw-cite-backlink"><b><a href="#cite_ref-Schwartz_Brooks_ACM_25-0">^</a></b></span> <span class="reference-text">
<cite class="citation cs2"><a rel="nofollow" class="external text" href="http://www.xent.com/FoRK-archive/july99/0646.html"><i>Origin of the term "byte", 1956</i></a>, <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170410125522/http://www.xent.com/FoRK-archive/july99/0646.html">archived</a> from the original on 2017-04-10<span class="reference-accessdate">, retrieved <span class="nowrap">2022-08-17</span></span></cite>
<blockquote class="templatequote"><div class="poem">
<p> A question-and-answer session at an <a href="ACM_conference" class="mw-redirect" title="ACM conference">ACM conference</a> on the history of programming languages included this exchange:<br>
<br>
[ <a href="John_Goodenough" class="mw-redirect" title="John Goodenough">John Goodenough</a>:<br>
You mentioned that the term "byte" is used in <a href="JOVIAL" title="JOVIAL">JOVIAL</a>. Where did the term come from? ]<br>
[ <a href="Jules_Schwartz" title="Jules Schwartz">Jules Schwartz</a> (inventor of JOVIAL):<br>
As I recall, the <a href="AN/FSQ-31" class="mw-redirect" title="AN/FSQ-31">AN/FSQ-31</a>, a totally different computer than the <a href="IBM_709" title="IBM 709">709</a>, was byte oriented. I don't recall for sure, but I'm reasonably certain the description of that computer included the word "byte," and we used it. ]<br>
[ <a href="Fred_Brooks" title="Fred Brooks">Fred Brooks</a>:<br>
May I speak to that? <a href="Werner_Buchholz" title="Werner Buchholz">Werner Buchholz</a> coined the word as part of the definition of <a href="IBM_STRETCH" class="mw-redirect" title="IBM STRETCH">STRETCH</a>, and the AN/FSQ-31 picked it up from STRETCH, but Werner is very definitely the author of that word. ]<br>
[ Schwartz:<br>
That's right. Thank you. ]
</p>
</div></blockquote>
<p class="mw-empty-elt">
</p>
</span></li>
<li id="cite_note-ibm.com-27"><span class="mw-cite-backlink"><b><a href="#cite_ref-ibm.com_27-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.ibm.com/support/knowledgecenter/SSGH4D_16.1.0/com.ibm.xlf161.aix.doc/language_ref/asciit.html">"List of EBCDIC codes by IBM"</a>. <i>ibm.com</i>. 2020-01-02. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200703073611/https://www.ibm.com/support/knowledgecenter/SSGH4D_16.1.0/com.ibm.xlf161.aix.doc/language_ref/asciit.html">Archived</a> from the original on 2020-07-03<span class="reference-accessdate">. Retrieved <span class="nowrap">2020-07-03</span></span>.</cite></span>
</li>
<li id="cite_note-Knuth-1-28"><span class="mw-cite-backlink">^ <a href="#cite_ref-Knuth-1_28-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Knuth-1_28-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFKnuth1997" class="citation book cs1">Knuth, Donald (1997) [1968]. <i>The Art of Computer Programming: Volume 1: Fundamental Algorithms</i> (3rd ed.). Boston: Addison-Wesley. p. 125. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9780201896831</bdi>.</cite></span>
</li>
<li id="cite_note-Williams_1969-29"><span class="mw-cite-backlink"><b><a href="#cite_ref-Williams_1969_29-0">^</a></b></span> <span class="reference-text">
<cite id="CITEREFWilliams1969" class="citation book cs1">Williams, R. H. (1969). <i>British Commercial Computer Digest: Pergamon Computer Data Series</i>. <a href="Pergamon_Press" title="Pergamon Press">Pergamon Press</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>1483122107</bdi>.</cite> <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1483122106</bdi>
</span>
</li>
<li id="cite_note-Philips_1971-30"><span class="mw-cite-backlink"><b><a href="#cite_ref-Philips_1971_30-0">^</a></b></span> <span class="reference-text">
<cite class="citation web cs1 cs1-prop-unfit"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20160304072023/http://www.intact-reunies.nl/pdf/product1971.pdf">"Philips Data Systems' product range"</a> <span class="cs1-format">(PDF)</span>. <a href="Philips" title="Philips">Philips</a>. April 1971. Archived from the original on 2016-03-04<span class="reference-accessdate">. Retrieved <span class="nowrap">2015-08-03</span></span>.</cite>
</span>
</li>
<li id="cite_note-IEC_Binary-31"><span class="mw-cite-backlink">^ <a href="#cite_ref-IEC_Binary_31-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-IEC_Binary_31-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><br>
[<br>
|*| About bits and bytes: prefixes for binary multiples - IEC<br>
|*| v0: <a rel="nofollow" class="external free" href="https://web.archive.org/web/20090818042050/http://www.iec.ch/online_news/etech/arch_2003/etech_0503/focus.htm">https://web.archive.org/web/20090818042050/http://www.iec.ch/online_news/etech/arch_2003/etech_0503/focus.htm</a><br>
|*| v1: <a rel="nofollow" class="external free" href="https://www.iec.ch/prefixes-binary-multiples">https://www.iec.ch/prefixes-binary-multiples</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210816011633/https://www.iec.ch/prefixes-binary-multiples">Archived</a> 2021-08-16 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> ]</span>
</li>
<li id="cite_note-NIST-32"><span class="mw-cite-backlink"><b><a href="#cite_ref-NIST_32-0">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://physics.nist.gov/cuu/Units/binary.html">Prefixes for Binary Multiples</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20070808000831/http://physics.nist.gov/cuu/Units/binary.html">Archived</a> 2007-08-08 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> — The NIST Reference on Constants, Units, and Uncertainty</span>
</li>
<li id="cite_note-33"><span class="mw-cite-backlink"><b><a href="#cite_ref-33">^</a></b></span> <span class="reference-text"><cite id="CITEREFMatsuokaSatoTatebeKoibuchi2014" class="citation journal cs1">Matsuoka, Satoshi; Sato, Hitoshi; Tatebe, Osamu; Koibuchi, Michihiro; Fujiwara, Ikki; Suzuki, Shuji; Kakuta, Masanori; Ishida, Takashi; Akiyama, Yutaka; Suzumura, Toyotaro; Ueno, Koji (2014-09-15). <a rel="nofollow" class="external text" href="https://superfri.org/index.php/superfri/article/view/24">"Extreme Big Data (EBD): Next Generation Big Data Infrastructure Technologies Towards Yottabyte/Year"</a>. <i>Supercomputing Frontiers and Innovations</i>. <b>1</b> (2): <span class="nowrap">89–</span>107. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.14529%2Fjsfi140206">10.14529/jsfi140206</a></span>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/2313-8734">2313-8734</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20220313085857/https://superfri.org/index.php/superfri/article/view/24">Archived</a> from the original on 2022-03-13<span class="reference-accessdate">. Retrieved <span class="nowrap">2022-05-27</span></span>.</cite></span>
</li>
<li id="cite_note-34"><span class="mw-cite-backlink"><b><a href="#cite_ref-34">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.bipm.org/documents/20126/64811223/Resolutions-2022.pdf">"List of Resolutions for the 27th meeting of the General Conference on Weights and Measures"</a> <span class="cs1-format">(PDF)</span>. 2022-11-18. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20221118153958/https://www.bipm.org/documents/20126/64811223/Resolutions-2022.pdf">Archived</a> <span class="cs1-format">(PDF)</span> from the original on 2022-11-18<span class="reference-accessdate">. Retrieved <span class="nowrap">2022-11-18</span></span>.</cite></span>
</li>
<li id="cite_note-35"><span class="mw-cite-backlink"><b><a href="#cite_ref-35">^</a></b></span> <span class="reference-text"><cite id="CITEREFGibney2022" class="citation journal cs1">Gibney, Elizabeth (18 November 2022). <span class="id-lock-subscription" title="Paid subscription required"><a rel="nofollow" class="external text" href="https://www.nature.com/articles/d41586-022-03747-9">"How many yottabytes in a quettabyte? Extreme numbers get new names"</a></span>. <i>Nature</i>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1038%2Fd41586-022-03747-9">10.1038/d41586-022-03747-9</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/0028-0836">0028-0836</a>. <a href="PMID_(identifier)" class="mw-redirect" title="PMID (identifier)">PMID</a> <a rel="nofollow" class="external text" href="https://pubmed.ncbi.nlm.nih.gov/36400954">36400954</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:253671538">253671538</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20230116065817/https://www.nature.com/articles/d41586-022-03747-9">Archived</a> from the original on 16 January 2023<span class="reference-accessdate">. Retrieved <span class="nowrap">21 November</span> 2022</span>.</cite></span>
</li>
<li id="cite_note-36"><span class="mw-cite-backlink"><b><a href="#cite_ref-36">^</a></b></span> <span class="reference-text">1977 Disk/Trend Report Rigid Disk Drives, published June 1977</span>
</li>
<li id="cite_note-37"><span class="mw-cite-backlink"><b><a href="#cite_ref-37">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://apac.sandisk.com/Products/Catalog(1349)-SanDisk_Extreme_Ducati_Edition_USB_Flash_Drive.aspx">SanDisk USB Flash Drive</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20080513155718/http://apac.sandisk.com/Products/Catalog%281349%29-SanDisk_Extreme_Ducati_Edition_USB_Flash_Drive.aspx">Archived</a> 2008-05-13 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> "Note: 1 megabyte (MB) = 1 million bytes; 1 gigabyte (GB) = 1 billion bytes."</span>
</li>
<li id="cite_note-apple-38"><span class="mw-cite-backlink">^ <a href="#cite_ref-apple_38-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-apple_38-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-apple_38-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://support.apple.com/en-us/HT201402">"How iOS and macOS report storage capacity"</a>. <i>Apple Support</i>. 27 February 2018. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200409170256/https://support.apple.com/en-us/HT201402">Archived</a> from the original on 9 April 2020<span class="reference-accessdate">. Retrieved <span class="nowrap">9 January</span> 2022</span>.</cite></span>
</li>
<li id="cite_note-39"><span class="mw-cite-backlink"><b><a href="#cite_ref-39">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://wiki.ubuntu.com/UnitsPolicy">"UnitsPolicy"</a>. <i>Ubuntu Wiki</i>. Ubuntu. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20211118114902/https://wiki.ubuntu.com/UnitsPolicy">Archived</a> from the original on 18 November 2021<span class="reference-accessdate">. Retrieved <span class="nowrap">9 January</span> 2022</span>.</cite></span>
</li>
<li id="cite_note-40"><span class="mw-cite-backlink"><b><a href="#cite_ref-40">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://wiki.debian.org/ConsistentUnitPrefixes">"ConsistentUnitPrefixes"</a>. <i>Debian Wiki</i>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20211203075715/https://wiki.debian.org/ConsistentUnitPrefixes">Archived</a> from the original on 3 December 2021<span class="reference-accessdate">. Retrieved <span class="nowrap">9 January</span> 2022</span>.</cite></span>
</li>
<li id="cite_note-41"><span class="mw-cite-backlink"><b><a href="#cite_ref-41">^</a></b></span> <span class="reference-text"><cite class="citation book cs1"><a rel="nofollow" class="external text" href="http://www.bitsavers.org/pdf/ibm/360/systemSummary/A22-6810-0_360sysSummary64.pdf#page=6">"Main Core Storage"</a> <span class="cs1-format">(PDF)</span>. <a rel="nofollow" class="external text" href="http://www.bitsavers.org/pdf/ibm/360/systemSummary/A22-6810-0_360sysSummary64.pdf"><i>IBM System/360 System Summary</i></a> <span class="cs1-format">(PDF)</span>. System Reference Library (First ed.). <a href="IBM" title="IBM">IBM</a>. 1964. p. 6. A22-6810-0<span class="reference-accessdate">. Retrieved <span class="nowrap">May 22,</span> 2025</span>.</cite></span>
</li>
<li id="cite_note-42"><span class="mw-cite-backlink"><b><a href="#cite_ref-42">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://docs.rs-online.com/41b6/0900766b8001b0a3.pdf#page=2">"5.25" Floppy Disk Drive Stock No. 237-088"</a> <span class="cs1-format">(PDF)</span>. <i>docs.rs-online.com</i>.</cite></span>
</li>
<li id="cite_note-43"><span class="mw-cite-backlink"><b><a href="#cite_ref-43">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://documents.westerndigital.com/content/dam/doc-library/en_us/assets/public/western-digital/collateral/white-paper/white-paper-advanced-format.pdf#page=3">"Advanced Format White Paper"</a> <span class="cs1-format">(PDF)</span>. <i>documents.westerndigital.com</i>.</cite></span>
</li>
<li id="cite_note-44"><span class="mw-cite-backlink"><b><a href="#cite_ref-44">^</a></b></span> <span class="reference-text"><cite id="CITEREFBrown2022" class="citation journal cs1">Brown, Richard J. C. (27 April 2022). "Reply to "Facing a shortage of the Latin letters for the prospective new SI symbols: alternative proposal for the new SI prefixes"". <i>Accreditation and Quality Assurance</i>. <b>27</b> (3): <span class="nowrap">143–</span>144. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1007%2Fs00769-022-01499-7">10.1007/s00769-022-01499-7</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:248397680">248397680</a>.</cite></span>
</li>
<li id="cite_note-45"><span class="mw-cite-backlink"><b><a href="#cite_ref-45">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.merriam-webster.com/dictionary/kilobyte">Kilobyte – Definition and More from the Free Merriam-Webster Dictionary</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20100409171320/http://www.merriam-webster.com/dictionary/kilobyte">Archived</a> 2010-04-09 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>. Merriam-webster.com (2010-08-13). Retrieved on 2011-01-07.</span>
</li>
<li id="cite_note-46"><span class="mw-cite-backlink"><b><a href="#cite_ref-46">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://dictionary.reference.com/browse/kilobyte">Kilobyte – Definition of Kilobyte at Dictionary.com</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20100901202451/http://dictionary.reference.com/browse/kilobyte">Archived</a> 2010-09-01 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>. Dictionary.reference.com (1995-09-29). Retrieved on 2011-01-07.</span>
</li>
<li id="cite_note-47"><span class="mw-cite-backlink"><b><a href="#cite_ref-47">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.askoxford.com/concise_oed/kilobyte?view=uk">Definition of kilobyte from Oxford Dictionaries Online</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20060625132017/http://www.askoxford.com/concise_oed/kilobyte?view=uk">Archived</a> 2006-06-25 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>. Askoxford.com. Retrieved on 2011-01-07.</span>
</li>
<li id="cite_note-48"><span class="mw-cite-backlink"><b><a href="#cite_ref-48">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="https://www.hpe.com/psnow/resources/ebooks/a00113994en_us_v2/Prefixes_for_Binary_and_Decimal_Multiples.html">Prefixes for Binary and Decimal Multiples: Binary versus decimal</a></span>
</li>
<li id="cite_note-auto-49"><span class="mw-cite-backlink"><b><a href="#cite_ref-auto_49-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://support.microsoft.com/kb/121839">"Determining Actual Disk Size: Why 1.44 MB Should Be 1.40 MB"</a>. Microsoft Support. 2003-05-06. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20140209012305/http://support.microsoft.com/kb/121839">Archived</a> from the original on 2014-02-09<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-03-25</span></span>.</cite></span>
</li>
<li id="cite_note-50"><span class="mw-cite-backlink"><b><a href="#cite_ref-50">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.vodafone.ie/planscosts_bus/data/">"3G/GPRS data rates"</a>. Vodafone Ireland. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20161026232743/https://www.vodafone.ie/planscosts_bus/data/">Archived</a> from the original on 26 October 2016<span class="reference-accessdate">. Retrieved <span class="nowrap">26 October</span> 2016</span>.</cite></span>
</li>
<li id="cite_note-51"><span class="mw-cite-backlink"><b><a href="#cite_ref-51">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.att.com/support_static_files/KB/KB24648.html">"Data Measurement Scale"</a>. AT&T<span class="reference-accessdate">. Retrieved <span class="nowrap">26 October</span> 2016</span>.</cite></span>
</li>
<li id="cite_note-52"><span class="mw-cite-backlink"><b><a href="#cite_ref-52">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20161026234911/https://www.orange.ro/recharge/internet.html">"Internet Mobile Access"</a>. Orange Romania. Archived from <a rel="nofollow" class="external text" href="https://www.orange.ro/recharge/internet.html">the original</a> on 26 October 2016<span class="reference-accessdate">. Retrieved <span class="nowrap">26 October</span> 2016</span>.</cite></span>
</li>
<li id="cite_note-53"><span class="mw-cite-backlink"><b><a href="#cite_ref-53">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.telstra.com.au/content/dam/tcom/personal/consumer-advice/pdf/intl-roaming.pdf">"Our Customer Terms"</a> <span class="cs1-format">(PDF)</span>. Telstra. p. 7. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170410020355/https://www.telstra.com.au/content/dam/tcom/personal/consumer-advice/pdf/intl-roaming.pdf">Archived</a> <span class="cs1-format">(PDF)</span> from the original on 10 April 2017<span class="reference-accessdate">. Retrieved <span class="nowrap">26 October</span> 2016</span>.</cite></span>
</li>
<li id="cite_note-pratt19820412-54"><span class="mw-cite-backlink"><b><a href="#cite_ref-pratt19820412_54-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFPratt1982" class="citation magazine cs1">Pratt, Allan D. (1982-04-12). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=YjAEAAAAMBAJ&pg=PA21">"Kwandary"</a>. Letters to the Editor. <i>InfoWorld</i>. p. 21<span class="reference-accessdate">. Retrieved <span class="nowrap">2025-03-16</span></span>.</cite></span>
</li>
<li id="cite_note-56"><span class="mw-cite-backlink"><b><a href="#cite_ref-56">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20140527094602/http://www.swtpc.com/mholley/SA400/SA400_Index.htm">"SA400 minifloppy"</a>. Swtpc.com. 2013-08-14. Archived from <a rel="nofollow" class="external text" href="http://www.swtpc.com/mholley/SA400/SA400_Index.htm">the original</a> on 2014-05-27<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-03-25</span></span>.</cite></span>
</li>
<li id="cite_note-57"><span class="mw-cite-backlink"><b><a href="#cite_ref-57">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20110608195322/http://www.swtpc.com/mholley/SA400/SA400_Datasheet.pdf">"Shugart Associates SA 400 minifloppy™ Disk Drive"</a> <span class="cs1-format">(PDF)</span>. Archived from <a rel="nofollow" class="external text" href="http://www.swtpc.com/mholley/SA400/SA400_Datasheet.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2011-06-08<span class="reference-accessdate">. Retrieved <span class="nowrap">2011-06-24</span></span>.</cite></span>
</li>
<li id="cite_note-58"><span class="mw-cite-backlink"><b><a href="#cite_ref-58">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20110423194129/http://www.bitsavers.org/pdf/dec/disc/rx01/EK-RX01-MM-002_maint_Dec76.pdf">"RXS/RX11 floppy disk system maintenance manual"</a> <span class="cs1-format">(PDF)</span>. Maynard, Massachusetts: Digital Equipment Corporation. May 1975. Archived from <a rel="nofollow" class="external text" href="http://bitsavers.org/pdf/dec/disc/rx01/EK-RX01-MM-002_maint_Dec76.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2011-04-23<span class="reference-accessdate">. Retrieved <span class="nowrap">2011-06-24</span></span>.</cite></span>
</li>
<li id="cite_note-59"><span class="mw-cite-backlink"><b><a href="#cite_ref-59">^</a></b></span> <span class="reference-text">IUCr 1995 Report - IUPAC Interdivisional Committee on Nomenclature and Symbols (IDCNS) <a rel="nofollow" class="external free" href="http://ww1.iucr.org/iucr-top/cexec/rep95/idcns.htm">http://ww1.iucr.org/iucr-top/cexec/rep95/idcns.htm</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20201219055254/http://ww1.iucr.org/iucr-top/cexec/rep95/idcns.htm">Archived</a> 2020-12-19 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></span>
</li>
<li id="cite_note-60"><span class="mw-cite-backlink"><b><a href="#cite_ref-60">^</a></b></span> <span class="reference-text">"Binary Prefix" University of Auckland Department of Computer Science <a rel="nofollow" class="external free" href="https://wiki.cs.auckland.ac.nz/stageonewiki/index.php/Binary_prefix">https://wiki.cs.auckland.ac.nz/stageonewiki/index.php/Binary_prefix</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20201016032232/https://wiki.cs.auckland.ac.nz/stageonewiki/index.php/Binary_prefix">Archived</a> 2020-10-16 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></span>
</li>
<li id="cite_note-61"><span class="mw-cite-backlink"><b><a href="#cite_ref-61">^</a></b></span> <span class="reference-text"><cite id="CITEREFNational_Institute_of_Standards_and_Technology" class="citation web cs1"><a href="National_Institute_of_Standards_and_Technology" title="National Institute of Standards and Technology">National Institute of Standards and Technology</a>. <a rel="nofollow" class="external text" href="http://physics.nist.gov/cuu/Units/binary.html">"Prefixes for binary multiples"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20070808000831/http://physics.nist.gov/cuu/Units/binary.html">Archived</a> from the original on 2007-08-08.</cite> "In December 1998 the <a href="International_Electrotechnical_Commission" title="International Electrotechnical Commission">International Electrotechnical Commission</a> (IEC) [...] approved as an IEC International Standard names and symbols for prefixes for binary multiples for use in the fields of data processing and data transmission."</span>
</li>
<li id="cite_note-kilobyte-62"><span class="mw-cite-backlink"><b><a href="#cite_ref-kilobyte_62-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www-cs-faculty.stanford.edu/~uno/news99.html">"What is a kilobyte?"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20110606103601/http://www-cs-faculty.stanford.edu/~uno/news99.html">Archived</a> from the original on 2011-06-06<span class="reference-accessdate">. Retrieved <span class="nowrap">2010-05-20</span></span>.</cite></span>
</li>
<li id="cite_note-63"><span class="mw-cite-backlink"><b><a href="#cite_ref-63">^</a></b></span> <span class="reference-text">NIST "Prefixes for binary multiples" <a rel="nofollow" class="external free" href="https://physics.nist.gov/cuu/Units/binary.html">https://physics.nist.gov/cuu/Units/binary.html</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180114113918/https://physics.nist.gov/cuu/Units/binary.html">Archived</a> 2018-01-14 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></span>
</li>
<li id="cite_note-64"><span class="mw-cite-backlink"><b><a href="#cite_ref-64">^</a></b></span> <span class="reference-text">Amendment 2 to IEC International Standard IEC 60027-2: Letter symbols to be used in electrical technology – Part 2: Telecommunications and electronics.</span>
</li>
<li id="cite_note-65"><span class="mw-cite-backlink"><b><a href="#cite_ref-65">^</a></b></span> <span class="reference-text"><cite id="CITEREFBarrow1997" class="citation web cs1">Barrow, Bruce (January 1997). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20051217152918/http://standards.ieee.org/reading/ieee/SB/Jan97/bearer_jan97.pdf">"A Lesson in Megabytes"</a> <span class="cs1-format">(PDF)</span>. <i>IEEE</i>. p. 5. Archived from <a rel="nofollow" class="external text" href="https://standards.ieee.org/reading/ieee/SB/Jan97/bearer_jan97.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 17 December 2005<span class="reference-accessdate">. Retrieved <span class="nowrap">14 December</span> 2024</span>.</cite></span>
</li>
<li id="cite_note-Order_Granting_Motion_to_Dismiss-66"><span class="mw-cite-backlink"><b><a href="#cite_ref-Order_Granting_Motion_to_Dismiss_66-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.courthousenews.com/wp-content/uploads/2020/01/flashdrives.pdf">"Order Granting Motion to Dismiss"</a> <span class="cs1-format">(PDF)</span>. <a href="United_States_District_Court_for_the_Northern_District_of_California" title="United States District Court for the Northern District of California">United States District Court for the Northern District of California</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20211007112246/https://www.courthousenews.com/wp-content/uploads/2020/01/flashdrives.pdf">Archived</a> <span class="cs1-format">(PDF)</span> from the original on 2021-10-07<span class="reference-accessdate">. Retrieved <span class="nowrap">2020-01-24</span></span>.</cite></span>
</li>
<li id="cite_note-WesternDigital-67"><span class="mw-cite-backlink">^ <a href="#cite_ref-WesternDigital_67-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-WesternDigital_67-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-WesternDigital_67-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFMook2006" class="citation web cs1">Mook, Nate (2006-06-28). <a rel="nofollow" class="external text" href="http://www.betanews.com/article/Western-Digital-Settles-Capacity-Suit/1151510648">"Western Digital Settles Capacity Suit"</a>. betanews. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20090907183334/http://www.betanews.com/article/Western-Digital-Settles-Capacity-Suit/1151510648">Archived</a> from the original on 2009-09-07<span class="reference-accessdate">. Retrieved <span class="nowrap">2009-03-30</span></span>.</cite></span>
</li>
<li id="cite_note-Baskin-2006-02-01-68"><span class="mw-cite-backlink"><b><a href="#cite_ref-Baskin-2006-02-01_68-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFBaskin2006" class="citation web cs1">Baskin, Scott D. (2006-02-01). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20090102041947/http://www.wdc.com/settlement/docs/document20.htm">"Defendant Western Digital Corporation's Brief in Support of Plaintiff's Motion for Preliminary Approval"</a>. <i>Orin Safier v. Western Digital Corporation</i>. <a href="Western_Digital_Corporation" class="mw-redirect" title="Western Digital Corporation">Western Digital Corporation</a>. Archived from <a rel="nofollow" class="external text" href="http://www.wdc.com/settlement/docs/document20.htm">the original</a> on 2009-01-02<span class="reference-accessdate">. Retrieved <span class="nowrap">2009-03-30</span></span>.</cite></span>
</li>
<li id="cite_note-Seagate-69"><span class="mw-cite-backlink"><b><a href="#cite_ref-Seagate_69-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFJudge2007" class="citation news cs1">Judge, Peter (2007-10-26). <a rel="nofollow" class="external text" href="https://www.zdnet.com/article/seagate-pays-out-over-gigabyte-definition/">"Seagate pays out over gigabyte definition"</a>. <i>ZDNet</i>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20140903033455/http://www.zdnet.com/seagate-pays-out-over-gigabyte-definition-3039290393/">Archived</a> from the original on 2014-09-03<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-09-16</span></span>.</cite></span>
</li>
<li id="cite_note-70"><span class="mw-cite-backlink"><b><a href="#cite_ref-70">^</a></b></span> <span class="reference-text">Allison Dexter, "How Many Words are in Harry Potter?", <a rel="nofollow" class="external autonumber" href="https://wordcounter.io/blog/how-many-words-are-in-harry-potter/">[1]</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210125205432/https://wordcounter.io/blog/how-many-words-are-in-harry-potter/">Archived</a> 2021-01-25 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>; shows <span class="nowrap">190<span style="margin-left:.25em;">637</span></span> words</span>
</li>
<li id="cite_note-71"><span class="mw-cite-backlink"><b><a href="#cite_ref-71">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.stanford.edu/class/cs101/bits-gigabytes.html">"Kilobytes Megabytes Gigabytes Terabytes (Stanford University)"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20201108095242/https://web.stanford.edu/class/cs101/bits-gigabytes.html">Archived</a> from the original on 2020-11-08<span class="reference-accessdate">. Retrieved <span class="nowrap">2020-12-12</span></span>.</cite></span>
</li>
<li id="cite_note-Hitachi1st-72"><span class="mw-cite-backlink"><b><a href="#cite_ref-Hitachi1st_72-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFPerenson2007" class="citation news cs1">Perenson, Melissa J. (4 January 2007). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20121024011417/http://www.pcworld.com/article/128400/article.html">"Hitachi Introduces 1-Terabyte Hard Drive"</a>. <i><a href="PC_World" title="PC World">www.pcworld.com</a></i>. Archived from <a rel="nofollow" class="external text" href="http://www.pcworld.com/article/128400/article.html">the original</a> on 24 October 2012<span class="reference-accessdate">. Retrieved <span class="nowrap">5 December</span> 2020</span>.</cite></span>
</li>
<li id="cite_note-computerweekly.com-73"><span class="mw-cite-backlink"><b><a href="#cite_ref-computerweekly.com_73-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20180128072952/http://www.computerweekly.com/feature/What-does-a-petabyte-look-like">"What does a petabyte look like?"</a>. Archived from <a rel="nofollow" class="external text" href="http://www.computerweekly.com/feature/What-does-a-petabyte-look-like">the original</a> on 28 January 2018<span class="reference-accessdate">. Retrieved <span class="nowrap">19 February</span> 2018</span>.</cite></span>
</li>
<li id="cite_note-74"><span class="mw-cite-backlink"><b><a href="#cite_ref-74">^</a></b></span> <span class="reference-text"><cite id="CITEREFGross2007" class="citation web cs1">Gross, Grant (24 November 2007). <a rel="nofollow" class="external text" href="https://www.pcworld.com/article/139885/article.html">"Internet Could Max Out in 2 Years, Study Says"</a>. <i><a href="PC_World" title="PC World">PC World</a></i>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20071126041511/http://www.pcworld.com/article/id,139885-pg,1/article.html">Archived</a> from the original on 26 November 2007<span class="reference-accessdate">. Retrieved <span class="nowrap">28 November</span> 2007</span>.</cite></span>
</li>
<li id="cite_note-75"><span class="mw-cite-backlink"><b><a href="#cite_ref-75">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://blogs.cisco.com/sp/the-zettabyte-era-officially-begins-how-much-is-that">"The Zettabyte Era Officially Begins (How Much is That?)"</a>. <i>Cisco Blogs</i>. 2016-09-09. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210802021532/https://blogs.cisco.com/sp/the-zettabyte-era-officially-begins-how-much-is-that">Archived</a> from the original on 2021-08-02<span class="reference-accessdate">. Retrieved <span class="nowrap">2021-08-04</span></span>.</cite></span>
</li>
<li id="cite_note-Cline_Bytes-76"><span class="mw-cite-backlink"><b><a href="#cite_ref-Cline_Bytes_76-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFCline" class="citation web cs1">Cline, Marshall. <a rel="nofollow" class="external text" href="https://isocpp.org/wiki/faq/intrinsic-types#very-large-bytes">"I could imagine a machine with 9-bit bytes. But surely not 16-bit bytes or 32-bit bytes, right?"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20190321232538/https://isocpp.org/wiki/faq/intrinsic-types#very-large-bytes">Archived</a> from the original on 2019-03-21<span class="reference-accessdate">. Retrieved <span class="nowrap">2015-06-18</span></span>.</cite></span>
</li>
<li id="cite_note-Klein_2008-77"><span class="mw-cite-backlink"><b><a href="#cite_ref-Klein_2008_77-0">^</a></b></span> <span class="reference-text">
<cite id="CITEREFKlein2008" class="citation cs2">Klein, Jack (2008), <a rel="nofollow" class="external text" href="https://web.archive.org/web/20100327225121/http://home.att.net/~jackklein/c/inttypes.html#char"><i>Integer Types in C and C++</i></a>, archived from <a rel="nofollow" class="external text" href="http://home.att.net/~jackklein/c/inttypes.html#char">the original</a> on 2010-03-27<span class="reference-accessdate">, retrieved <span class="nowrap">2015-06-18</span></span></cite>
</span>
</li>
<li id="cite_note-Cline_FAQ-79"><span class="mw-cite-backlink"><b><a href="#cite_ref-Cline_FAQ_79-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFCline" class="citation web cs1">Cline, Marshall. <a rel="nofollow" class="external text" href="https://isocpp.org/wiki/faq/intrinsic-types#bytes-review">"C++ FAQ: the rules about bytes, chars, and characters"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20190321232538/https://isocpp.org/wiki/faq/intrinsic-types#bytes-review">Archived</a> from the original on 2019-03-21<span class="reference-accessdate">. Retrieved <span class="nowrap">2015-06-18</span></span>.</cite></span>
</li>
<li id="cite_note-NWU-80"><span class="mw-cite-backlink"><b><a href="#cite_ref-NWU_80-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.ece.northwestern.edu/local-apps/matlabhelp/techdoc/matlab_external/ch_seri8.html">"External Interfaces/API"</a>. Northwestern University. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180809063331/http://www.ece.northwestern.edu/local-apps/matlabhelp/techdoc/matlab_external/ch_seri8.html">Archived</a> from the original on 2018-08-09<span class="reference-accessdate">. Retrieved <span class="nowrap">2016-09-02</span></span>.</cite></span>
</li>
</ol></div></div>
<div class="mw-heading mw-heading2"><h2 id="Further_reading">Further reading</h2></div>
<ul><li><cite class="citation book cs1"><a rel="nofollow" class="external text" href="http://bitsavers.org/pdf/dec/pdp10/1970_PDP-10_Ref/1970PDP10Ref_Part1.pdf#page=33">"2.5 Byte manipulation"</a> <span class="cs1-format">(PDF)</span>. <a rel="nofollow" class="external text" href="http://bitsavers.org/pdf/dec/pdp10/1970_PDP-10_Ref/1970PDP10Ref_Part1.pdf"><i>Programming with the PDP-10 Instruction Set</i></a> <span class="cs1-format">(PDF)</span>. PDP-10 System Reference Manual. Vol. 1. <a href="Digital_Equipment_Corporation" title="Digital Equipment Corporation">Digital Equipment Corporation</a> (DEC). August 1969. pp. <span class="nowrap">2-15 –</span> <span class="nowrap">2-17</span>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170405154620/http://bitsavers.informatik.uni-stuttgart.de/pdf/dec/pdp10/1970_PDP-10_Ref/1970PDP10Ref_Part1.pdf">Archived</a> <span class="cs1-format">(PDF)</span> from the original on 2017-04-05<span class="reference-accessdate">. Retrieved <span class="nowrap">2017-04-05</span></span>.</cite></li>
<li>Ashley Taylor. "Bits and Bytes". Stanford. <a rel="nofollow" class="external free" href="https://web.stanford.edu/class/cs101/bits-bytes.html">https://web.stanford.edu/class/cs101/bits-bytes.html</a></li></ul>
<div class="navbox-styles"><style data-mw-deduplicate="TemplateStyles:r1236075235">
/* start https://en.wikipedia.org/ */
.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}
/* end https://en.wikipedia.org/ */
</style></div><div role="navigation" class="navbox" aria-labelledby="Units_of_information107" style="padding:3px"><table class="nowraplinks mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><div id="Units_of_information107" style="font-size:114%;margin:0 4em"><a href="Units_of_information" title="Units of information">Units of information</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Platform-independent units</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Bit" title="Bit">bit</a></li>
<li><a href="Hextet" title="Hextet">hextet</a></li>
<li><a href="Octet_(computing)" title="Octet (computing)">octet</a></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Platform-dependent units</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Nibble" title="Nibble">nibble</a></li>
<li><a href="Syllable_(computing)" title="Syllable (computing)">syllable</a></li>
<li><a href="Word_(computer_architecture)" title="Word (computer architecture)">word</a></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Metric bit units</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Kilobit" class="mw-redirect" title="Kilobit">kilobit</a></li>
<li><a href="Megabit" class="mw-redirect" title="Megabit">megabit</a></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Metric byte units</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Kilobyte" title="Kilobyte">kilobyte</a></li>
<li><a href="Megabyte" title="Megabyte">megabyte</a></li>
<li><a href="Gigabyte" title="Gigabyte">gigabyte</a></li></ul>
</div></td></tr></tbody></table></div>
<div class="navbox-styles"></div><div role="navigation" class="navbox" aria-labelledby="Data_types177" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><div id="Data_types177" style="font-size:114%;margin:0 4em"><a href="Data_type" title="Data type">Data types</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Units_of_information" title="Units of information">Uninterpreted</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Bit" title="Bit">Bit</a></li>
<li><a href="Ternary_numeral_system" title="Ternary numeral system">Trit</a></li>
<li><a href="Ternary_numeral_system#Tryte" title="Ternary numeral system">Tryte</a></li>
<li><a href="Word_(computer_architecture)" title="Word (computer architecture)">Word</a></li>
<li><a href="Bit_array" title="Bit array">Bit array</a></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Numeric</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Arbitrary-precision_arithmetic" title="Arbitrary-precision arithmetic">Arbitrary-precision or bignum</a></li>
<li><a href="Complex_data_type" title="Complex data type">Complex</a></li>
<li><a href="Decimal_data_type" title="Decimal data type">Decimal</a></li>
<li><a href="Fixed-point_arithmetic" title="Fixed-point arithmetic">Fixed point</a></li>
<li><a href="Block_floating_point" title="Block floating point">Block floating point</a></li>
<li><a href="Floating-point_arithmetic" title="Floating-point arithmetic">Floating point</a>
<ul><li>Reduced precision
<ul><li><a href="Minifloat" title="Minifloat">Minifloat</a></li>
<li><a href="Half-precision_floating-point_format" title="Half-precision floating-point format">Half precision</a></li>
<li><a href="Bfloat16_floating-point_format" title="Bfloat16 floating-point format">bfloat16</a></li></ul></li>
<li><a href="Single-precision_floating-point_format" title="Single-precision floating-point format">Single precision</a></li>
<li><a href="Double-precision_floating-point_format" title="Double-precision floating-point format">Double precision</a></li>
<li><a href="Quadruple-precision_floating-point_format" title="Quadruple-precision floating-point format">Quadruple precision</a></li>
<li><a href="Octuple-precision_floating-point_format" title="Octuple-precision floating-point format">Octuple precision</a></li>
<li><a href="Extended_precision" title="Extended precision">Extended precision</a>
<ul><li><a href="Long_double" title="Long double">Long double</a></li></ul></li></ul></li>
<li><a href="Integer_(computer_science)" title="Integer (computer science)">Integer</a>
<ul><li><a href="Signedness" title="Signedness">signedness</a></li></ul></li>
<li><a href="Interval_arithmetic#Implementations" title="Interval arithmetic">Interval</a></li>
<li><a href="Rational_data_type" title="Rational data type">Rational</a></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Pointer_(computer_programming)" title="Pointer (computer programming)">Pointer</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Memory_address" title="Memory address">Address</a>
<ul><li><a href="Physical_address" title="Physical address">physical</a></li>
<li><a href="Virtual_address_space" title="Virtual address space">virtual</a></li></ul></li>
<li><a href="Reference_(computer_science)" title="Reference (computer science)">Reference</a></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Plain_text" title="Plain text">Text</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Character_(computing)" title="Character (computing)">Character</a></li>
<li><a href="String_(computer_science)" title="String (computer science)">String</a>
<ul><li><a href="Null-terminated_string" title="Null-terminated string">null-terminated</a></li></ul></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Composite_data_type" title="Composite data type">Composite</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Algebraic_data_type" title="Algebraic data type">Algebraic data type</a>
<ul><li><a href="Generalized_algebraic_data_type" title="Generalized algebraic data type">generalized</a></li></ul></li>
<li><a href="Array_(data_type)" title="Array (data type)">Array</a></li>
<li><a href="Associative_array" title="Associative array">Associative array</a></li>
<li><a href="Class_(computer_programming)" title="Class (computer programming)">Class</a></li>
<li><a href="Dependent_type" title="Dependent type">Dependent</a></li>
<li><a href="Intuitionistic_type_theory#Equality_type" title="Intuitionistic type theory">Equality</a></li>
<li><a href="Inductive_type" title="Inductive type">Inductive</a></li>
<li><a href="Intersection_type" title="Intersection type">Intersection</a></li>
<li><a href="List_(abstract_data_type)" title="List (abstract data type)">List</a></li>
<li><a href="Object_(computer_science)" title="Object (computer science)">Object</a>
<ul><li><a href="Metaobject" title="Metaobject">metaobject</a></li></ul></li>
<li><a href="Option_type" title="Option type">Option type</a></li>
<li><a href="Product_type" title="Product type">Product</a></li>
<li><a href="Record_(computer_science)" title="Record (computer science)">Record or Struct</a></li>
<li><a href="Refinement_type" title="Refinement type">Refinement</a></li>
<li><a href="Set_(abstract_data_type)" title="Set (abstract data type)">Set</a></li>
<li><a href="Union_type" title="Union type">Union</a>
<ul><li><a href="Tagged_union" title="Tagged union">tagged</a></li></ul></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Other</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Boolean_data_type" title="Boolean data type">Boolean</a></li>
<li><a href="Bottom_type" title="Bottom type">Bottom type</a></li>
<li><a href="Container_(abstract_data_type)" title="Container (abstract data type)">Collection</a></li>
<li><a href="Enumerated_type" title="Enumerated type">Enumerated type</a></li>
<li><a href="Exception_handling" title="Exception handling">Exception</a></li>
<li><a href="Function_type" title="Function type">Function type</a></li>
<li><a href="Opaque_data_type" title="Opaque data type">Opaque data type</a></li>
<li><a href="Recursive_data_type" title="Recursive data type">Recursive data type</a></li>
<li><a href="Semaphore_(programming)" title="Semaphore (programming)">Semaphore</a></li>
<li><a href="Stream_(computing)" title="Stream (computing)">Stream</a></li>
<li><a href="Strongly_typed_identifier" title="Strongly typed identifier">Strongly typed identifier</a></li>
<li><a href="Top_type" class="mw-redirect" title="Top type">Top type</a></li>
<li><a href="Type_class" title="Type class">Type class</a></li>
<li><a href="Empty_type" title="Empty type">Empty type</a></li>
<li><a href="Unit_type" title="Unit type">Unit type</a></li>
<li><a href="Void_type" title="Void type">Void</a></li></ul>
</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Related<br>topics</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">
<ul><li><a href="Abstract_data_type" title="Abstract data type">Abstract data type</a></li>
<li><a href="Boxing_(computer_programming)" title="Boxing (computer programming)">Boxing</a></li>
<li><a href="Data_structure" title="Data structure">Data structure</a></li>
<li><a href="Generic_programming" title="Generic programming">Generic</a></li>
<li><a href="Kind_(type_theory)" title="Kind (type theory)">Kind</a>
<ul><li><a href="Metaclass" title="Metaclass">metaclass</a></li></ul></li>
<li><a href="Parametric_polymorphism" title="Parametric polymorphism">Parametric polymorphism</a></li>
<li><a href="Primitive_data_type" title="Primitive data type">Primitive data type</a></li>
<li><a href="Interface_(object-oriented_programming)" title="Interface (object-oriented programming)">Interface</a></li>
<li><a href="Subtyping" title="Subtyping">Subtyping</a></li>
<li><a href="Type_constructor" title="Type constructor">Type constructor</a></li>
<li><a href="Type_conversion" title="Type conversion">Type conversion</a></li>
<li><a href="Type_system" title="Type system">Type system</a></li>
<li><a href="Type_theory" title="Type theory">Type theory</a></li>
<li><a href="Variable_(computer_science)" title="Variable (computer science)">Variable</a></li></ul>
</div></td></tr></tbody></table></div></div><!--htdig_noindex--><div><div class="zim-footer">
This article is issued from <a class="external text" title="Last edited on 2025-08-07" href="https://en.wikipedia.org/wiki/?title=Byte&oldid=1304738935">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.
</div>
</div><!--/htdig_noindex--></div>
</div>
</main>
</div>
</div>
</div>
</body></html>